Skip to content

RUM-10726: Add more info about mobile sdk benchmarking #30301

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

RUM-10726: Add more info about mobile sdk benchmarking #30301

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions config/_default/menus/main.en.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7524,6 +7524,11 @@ menu:
parent: rum_mobile_android
identifier: rum_mobile_android_troubleshooting
weight: 110
- name: Performance overhead
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- name: Performance overhead
- name: SDK Performance Impact

url: real_user_monitoring/mobile_and_tv_monitoring/android/performance_overhead
parent: rum_mobile_android
identifier: rum_mobile_android_performance_overhead
weight: 111
- name: iOS and tvOS
url: real_user_monitoring/mobile_and_tv_monitoring/ios
parent: mobile_and_tv_monitoring
Expand Down
1 change: 1 addition & 0 deletions content/en/real_user_monitoring/mobile_and_tv_monitoring/android/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,4 +34,5 @@ To get started with RUM for Android, create an application and configure the And
{{< nextlink href="/real_user_monitoring/mobile_and_tv_monitoring/android/troubleshooting">}}
<u>Troubleshooting</u>: Common troubleshooting Android SDK issues.{{< /nextlink >}}
{{< nextlink href="/real_user_monitoring/mobile_and_tv_monitoring/android/jetpack_compose_instrumentation">}}<u>Jetpack Compose Instrumentation</u>: Instrument Jetpack Compose manually or automatically using the Datadog Gradle Plugin. {{< /nextlink >}}
{{< nextlink href="/real_user_monitoring/mobile_and_tv_monitoring/android/performance_overhead">}}<u>Performance overhead</u>: Learn about how SDK impacts performance of your application. {{< /nextlink >}}
{{< /whatsnext >}}
32 changes: 32 additions & 0 deletions ...n/real_user_monitoring/mobile_and_tv_monitoring/android/performance_overhead.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
---
title: Performance overhead
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: Performance overhead
title: SDK Performance Impact

description: Learn about how SDK impacts performance of your application.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
description: Learn about how SDK impacts performance of your application.
description: Learn about how the SDK impacts performance of your application.

aliases:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This parameter is really for previously existing pages that have been moved.

Suggested change
aliases:

- /real_user_monitoring/mobile_and_tv_monitoring/performance_overhead/android
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- /real_user_monitoring/mobile_and_tv_monitoring/performance_overhead/android

further_reading:
- link: https://github.com/DataDog/dd-sdk-android
tag: "Source Code"
text: dd-sdk-android Source code
- link: /real_user_monitoring
tag: Documentation
text: Explore Real User Monitoring
---

## Performance overhead measurements
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Performance overhead measurements
## Overview


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When integrating any SDK into your Android application, understanding its performance impact is crucial for maintaining a smooth user experience. The Datadog RUM SDK is designed with performance in mind and provides transparent measurements to help you make informed decisions.

You can read the following pages with detailed explanation of how we measure performance overhead of the SDK: [Android][1], [iOS][2].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
You can read the following pages with detailed explanation of how we measure performance overhead of the SDK: [Android][1], [iOS][2].
You can read the following pages with detailed explanation of how we measure performance overhead of the SDK: [Android][1], [iOS][2]. These resources include specific metrics, benchmarks, and real-world performance data to help you understand exactly how the SDK affects your app's performance.


## Continuous benchmarks

We also have an internal infrastructure of continuous benchmarking. There is an internal set of ui tests that run on a special benchmark application for every change made to the sdk. This way we are able to detect performance regression early and don't allow the corresponding changes to be included in the following release.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We also have an internal infrastructure of continuous benchmarking. There is an internal set of ui tests that run on a special benchmark application for every change made to the sdk. This way we are able to detect performance regression early and don't allow the corresponding changes to be included in the following release.
Datadog has an internal infrastructure of continuous benchmarking. There is an internal set of UI tests that run on a special benchmark application for every change made to the SDK. This way Datadog is able to detect performance regression early to ensure that they are prevented from reaching production releases.


You can find the source code of the benchmark app here: [Android][3], [iOS][4].

## Further Reading

{{< partial name="whats-next/whats-next.html" >}}

[1]: https://github.com/DataDog/dd-sdk-android/blob/develop/docs/sdk_performance.md
[2]: https://github.com/DataDog/dd-sdk-ios/blob/develop/docs/session_replay_performance.md
[3]: https://github.com/DataDog/dd-sdk-android/tree/develop/sample/benchmark
[4]: https://github.com/DataDog/dd-sdk-ios/tree/develop/BenchmarkTests
7 changes: 6 additions & 1 deletion content/en/real_user_monitoring/session_replay/mobile/app_performance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,13 @@ To minimize the total upload volume, Datadog employs a highly optimized wire for
## Application size
Datadog's SDK follows strict standards and aims to minimize the inclusion of third-party dependencies. This approach ensures that the SDK leverages as much native framework code as possible. On Android, the binary size produced by Datadog's own code in the AAR package is 480 kB. See more information on the application size impact [here][1]. On iOS, the size of exported `*.ipa` file will be higher by approximately 200 kB.

## Benchmarks
For more detailed description of how Session Replay performance overhead was measured you can visit the following pages: [Android][2], [iOS][3].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For more detailed description of how Session Replay performance overhead was measured you can visit the following pages: [Android][2], [iOS][3].
For a more detailed description of how Session Replay performance overhead was measured, see the following pages: [Android][2], [iOS][3].


## Further reading

{{< partial name="whats-next/whats-next.html" >}}

[1]: https://github.com/DataDog/dd-sdk-android/blob/develop/docs/sdk_performance.md?plain=1#L119
[1]: https://github.com/DataDog/dd-sdk-android/blob/develop/docs/sdk_performance.md?plain=1#L119
[2]: https://github.com/DataDog/dd-sdk-android/blob/develop/docs/sdk_performance.md#session-relay-performance-measurement
[3]: https://github.com/DataDog/dd-sdk-ios/blob/develop/docs/session_replay_performance.md
Loading