Skip to content

Commit d09bbb1

Browse files
RUM-10726: Add more info about mobile sdk benchmarking
1 parent 095f6a6 commit d09bbb1

File tree

4 files changed

+62
-1
lines changed

4 files changed

+62
-1
lines changed

config/_default/menus/main.en.yaml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7524,6 +7524,11 @@ menu:
75247524
parent: rum_mobile_android
75257525
identifier: rum_mobile_android_troubleshooting
75267526
weight: 110
7527+
- name: Performance overhead
7528+
url: real_user_monitoring/mobile_and_tv_monitoring/android/performance_overhead
7529+
parent: rum_mobile_android
7530+
identifier: rum_mobile_android_performance_overhead
7531+
weight: 111
75277532
- name: iOS and tvOS
75287533
url: real_user_monitoring/mobile_and_tv_monitoring/ios
75297534
parent: mobile_and_tv_monitoring

content/en/real_user_monitoring/mobile_and_tv_monitoring/android/_index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,4 +34,5 @@ To get started with RUM for Android, create an application and configure the And
3434
{{< nextlink href="/real_user_monitoring/mobile_and_tv_monitoring/android/troubleshooting">}}
3535
<u>Troubleshooting</u>: Common troubleshooting Android SDK issues.{{< /nextlink >}}
3636
{{< 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 >}}
37+
{{< 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 >}}
3738
{{< /whatsnext >}}
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
title: Performance overhead
3+
description: Learn about how SDK impacts performance of your application.
4+
aliases:
5+
- /real_user_monitoring/mobile_and_tv_monitoring/performance_overhead/android
6+
further_reading:
7+
- link: https://github.com/DataDog/dd-sdk-android
8+
tag: "Source Code"
9+
text: dd-sdk-android Source code
10+
- link: /real_user_monitoring
11+
tag: Documentation
12+
text: Explore Real User Monitoring
13+
---
14+
15+
## Overview
16+
17+
Some benchmarks.
18+
19+
## Check if Datadog RUM is initialized
20+
Use the utility method `isInitialized` to check if the SDK is properly initialized:
21+
22+
```kotlin
23+
if (Datadog.isInitialized()) {
24+
// your code here
25+
}
26+
```
27+
28+
## Debugging
29+
When writing your application, you can enable development logs by calling the `setVerbosity` method. All internal messages in the library with a priority equal to or higher than the provided level are then logged to Android's Logcat:
30+
31+
```kotlin
32+
Datadog.setVerbosity(Log.INFO)
33+
```
34+
35+
## Migrating to 2.0.0
36+
37+
If you've been using the SDK v1, there are some breaking changes introduced in version `2.0.0`. See the [migration guide][2] for more information.
38+
39+
## "Deobfuscation failed" warning
40+
41+
A warning appears when deobfuscation fails for a stack trace. If the stack trace is not obfuscated to begin with, you can ignore this warning. Otherwise, use the [RUM Debug Symbols page][3] to view all your uploaded mapping files. See [Investigate Obfuscated Stack Traces with RUM Debug Symbols][4].
42+
43+
## Further Reading
44+
45+
{{< partial name="whats-next/whats-next.html" >}}
46+
47+
[1]: /help
48+
[2]: https://github.com/DataDog/dd-sdk-android/blob/develop/MIGRATION.MD
49+
[3]: https://app.datadoghq.com/source-code/setup/rum
50+
[4]: /real_user_monitoring/guide/debug-symbols

content/en/real_user_monitoring/session_replay/mobile/app_performance.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,13 @@ To minimize the total upload volume, Datadog employs a highly optimized wire for
3636
## Application size
3737
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.
3838

39+
## Benchmarks
40+
For more detailed description of how Session Replay performance overhead was measured you can visit the following pages: [Android][2], [iOS][3].
41+
3942
## Further reading
4043

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

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

0 commit comments

Comments
 (0)