Split RUM SDK performance impact docs #32685
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,52 @@ | ||||||
| --- | ||||||
| title: SDK Performance Impact | ||||||
| description: Learn about how the SDK impacts performance of your application. | ||||||
| aliases: | ||||||
| - /real_user_monitoring/mobile_and_tv_monitoring/ios/sdk_performance_impact | ||||||
| further_reading: | ||||||
| - link: https://github.com/DataDog/dd-sdk-ios | ||||||
| tag: "Source Code" | ||||||
| text: dd-sdk-ios Source code | ||||||
| - link: /real_user_monitoring | ||||||
| tag: Documentation | ||||||
| text: Explore Real User Monitoring | ||||||
| --- | ||||||
|
|
||||||
| ## Overview | ||||||
|
|
||||||
| When integrating any SDK into your iOS 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. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| ## Performance impact benchmarks | ||||||
|
|
||||||
| To simulate the typical usage of Datadog SDK, it was integrated into the [Beam][3] application and typical user behavior (scrolling the feed, browsing reddits) was simulated. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| The SDK features that were used: | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
| 1. Basic RUM instrumentation for tracking views, actions, and resources | ||||||
| 2. Logging | ||||||
| 3. Tracing | ||||||
|
|
||||||
| Below are the results of the measurements. | ||||||
|
|
||||||
| | Measurement | with SDK | without SDK | | ||||||
| |-------------------|---------------------------------|-------------| | ||||||
| | Peak CPU Usage | 44% | 40% | | ||||||
| | Peak Memory Usage | 72.4 MB | 67.96 MB | | ||||||
| | App startup time | 0.894 ms | 0.649 ms | | ||||||
| | Bundle size | 23.6 MB | 22.2 MB | | ||||||
| | Network usage | 21.88 KB sent, 1.68 KB received | n/a | | ||||||
|
|
||||||
| You can read the following [page][1] for more details about these benchmarks. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| ## Continuous benchmarks | ||||||
|
|
||||||
| 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. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| You can find the source code of the benchmark app [here][2]. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| ## Further Reading | ||||||
|
|
||||||
| {{< partial name="whats-next/whats-next.html" >}} | ||||||
|
|
||||||
| [2]: https://github.com/DataDog/dd-sdk-ios/blob/develop/docs/sdk_performance.md | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
| [4]: https://github.com/DataDog/dd-sdk-ios/tree/develop/BenchmarkTests | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
| [3]: https://github.com/awkward/beam | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.