Update docs/platforms/android/session-replay/performance-overhead.mdx

Co-authored-by: Liza Mock <[email protected]>

Author: romtsn

docs/platforms/android/session-replay/performance-overhead.mdx

@@ -5,9 +5,22 @@ notSupported:
 description: "Learn about how enabling Session Replay impacts the performance of your application."
 ---
 
-The only way to get accurate metrics is to measure performance overhead yourself. You can apply realistic access patterns against your own application, and correlate that to your own topline business metrics. You can learn more about the various optimizations implemented in the Android Replay SDK in the [Replay Performance Overhead](/product/explore/session-replay/mobile/performance-overhead/) documentation.
+If you're considering enabling Session Replay, it's important to first understand the potential performance impact to your app. While accurate metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics, to provide a baseline, we measured the overhead using the open-source [Pocket Casts](https://github.com/Automattic/pocket-casts-android) app. 
 
-We measured the overhead of the Android Replay SDK using the [Pocket Casts](https://github.com/Automattic/pocket-casts-android) open-source app, which includes a diverse set of components such as Fragments, Activities, and Jetpack Compose screens. The benchmarks were conducted with full masking enabled, using optimized release builds, and running through the same user flow 10 times. This approach ensured the measurements closely reflect the overhead in a real-world application. Here are the results (median values are shown):
+You can learn more about the various optimizations implemented in the Android Replay SDK in the [Replay Performance Overhead](/product/explore/session-replay/mobile/performance-overhead/) docs.
+
+## Benchmarking the Android Replay SDK
+
+The Pocket Casts app offers a diverse mix of components, including Fragments, Activities, and Jetpack Compose screens, making it an ideal candidate for testing. Here's how the benchmarks were conducted:
+
+- **Configuration:** Full masking was enabled, and optimized release builds were used.
+- **User Flow:** The same flow was executed 10 times to ensure consistency.
+- **Real-World Representation:** This approach closely mirrors performance in real-world scenarios.
+
+The benchmarks were run on a Pixel 2XL with Android 11.
+
+### Results
+Below are the results of the benchmarking tests, presented as median values to reflect typical overhead.
 
 | Metric                           | Sentry SDK only | Sentry + Replay SDK |
 | -------------------------------- | --------------- | ------------------- |