Impact on performance
We always strive to be non-intrusive, and transparent to the developers of the client app. We apply this rule on the performance as well. These are the technical specifics we can share on performance, if you have any questions feel free to reach out to us.
The performance results were obtained under the following conditions:
| Condition | Value |
|---|---|
| Device model | Pixel 5 |
| Android version | 33 (Android 13) |
| Property | Value |
|---|---|
| SDK size | 1721 KB |
| Nbr. of methods | 8217 |
| Nbr. of fields | 4495 |
| RAM usage | <4 MB |
| SDK CPU peak on event | <15 % |
| Data transmitted over network for a default batch size of 50 events. The size of the batch can be customized if needed. | ~25kb |
Performance test procedure
Section titled Performance test procedure| CPU Usage Test | RAM Usage Test | Memory Leak Test |
|---|---|---|
| We are profiling our Demo app with and without the SDK dependency by following the same use case. | We are profiling our Demo app with and without the SDK dependency by following the same use case. | We are profiling our demo app and we are using the Adb Monkey tool to create random user input events |
| We are measuring the CPU peak for both versions of the app and we are computing the difference | We are measuring the RAM usage peak for both versions of the app and we are computing the difference | During this time we are monitoring the RAM behavior for any anomaly. We are using the Memory Profiler to track/fix the issue |