---
title: Impact on performance - Android (classic)
description: Metrics to evaluate the impact on performance of the SDK on your apps
lastUpdated: 16 March 2026
source_url:
  html: https://docs.contentsquare.com/en/android/impact-on-performance/
  md: https://docs.contentsquare.com/en/android/impact-on-performance/index.md
---

> Documentation index: https://docs.contentsquare.com/llms.txt
> Use this file to discover all available pages before exploring further.

The latest CSQ SDK is here! Learn how to [upgrade your app](https://docs.contentsquare.com/en/csq-sdk-android/experience-analytics/upgrade-from-cs-sdk/).

Contentsquare strives to be non-intrusive and transparent to client app developers. The following metrics help you evaluate the performance impact of the Contentsquare SDK on your apps.

## Performance impact

The following are the technical specifics we can share on performance.

The performance results were obtained under the following conditions:

| Condition | Value |
| - | - |
| Device model | Pixel 5 |
| Android version | 34 (Android 14) |

Note

The numbers provided below will vary depending on the user's device and Android version.

| Property | Value |
| - | - |
| SDK size | 1567 KB |
| Nbr. of methods | 5753 |
| Nbr. of fields | 3701 |
| 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

| 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 |