Reducing Android scope-sync overhead in Sentry Flutter

Summary

The Sentry Flutter SDK records breadcrumbs, user information, and diagnostic data through scope updates, adding overhead to apps. On Android, a dedicated worker isolate handles Sentry Android SDK operations to avoid blocking the main UI isolate, but both the calling isolate and the worker normalized the same data, and the encoding step produced a JSON string plus an unnecessary byte buffer copy. Removing the duplicate normalization roughly halved normalization time, while using JsonUtf8Encoder to encode directly into UTF-8 bytes reduced encoding time by 16% and eliminated the extra copy. Combined, these changes reduced total scope payload processing time by 27–30% for benchmark inputs of 1.2 KB, 23 KB, and 238 KB, as measured on a Google Pixel 4 in release mode. The optimizations are available in sentry_flutter version 9.26.0 and later.

Takeaways

1. 1

   Duplicate normalization of scope data between the calling isolate and the worker roughly doubled normalization time. Removing the second normalization cut normalization time by about 50% for benchmarked inputs.

2. 2

   Using JsonUtf8Encoder to produce UTF-8 bytes directly eliminated an extra buffer copy and reduced encoding benchmark time by 16% for both small and large payloads.

3. 3

   Combined normalization and encoding optimizations reduced total scope payload processing time by 27–30% across benchmark input sizes on a Google Pixel 4 in release mode.

FAQ