Comprehensive Guide to iOS Performance Testing: CPU, Stutter, Network, and Energy

Background: Performance testing is essential for every iOS developer; without proper profiling, apps may suffer from lag or crashes, leading to poor user experience.

CPU Monitoring

Use Activity Monitor (Profile > Activity Monitor) to record CPU and memory peaks while running the app, then compare multiple runs and keep the worst case as the final result.

Stutter Analysis

Stutter can be caused by CPU or GPU resource consumption. After ruling out CPU with the above tool, focus on GPU using Instruments and custom code.

1. Code‑based GPU Monitoring

A.profile>ActivityMonitor 启动 APP,运行过程中option选择峰值查看 cpu和内存使用量。

Various GPU‑related tools are listed: GPU Driver, Core Animation, OpenGL ES Driver, and the Color Debug Options in the simulator.

GPU Driver Metrics

Device Utilization % – overall GPU time; >95% means the app is GPU‑bound.

Renderer Utilization % – time spent drawing pixels; >50% may indicate over‑draw or off‑screen rendering.

Tiler Utilization % – time spent processing vertices; >50% suggests too many layers.

Split count – number of frame splits caused by vertex overflow.

Step‑by‑step UI Performance Diagnosis

Check frame rate (aim for ~60 fps).

Identify bottleneck (CPU vs GPU).

Remove unnecessary CPU drawing (e.g., avoid overriding drawRect when not needed).

Reduce off‑screen rendering.

Minimize blending layers.

Use PNG images and appropriate sizes to let the GPU handle them.

Avoid heavy effects such as UIBlurEffect unless required.

Keep view hierarchy clean; avoid frequent add/remove of views.

Core Animation Checks

Color Blended Layers – red indicates blended layers, green indicates opaque layers.

Color Hits Green and Misses Red – shows rasterization cache reuse (green) or frequent recreation (red).

Color Copied Images – highlights images in unsupported color formats that force CPU rendering.

Color Misaligned Images – warns about scaled or misaligned pixels.

Color Offscreen‑Rendered Yellow – highlights layers that trigger off‑screen rendering.

Network Testing

Two main approaches:

Network Link Conditioner – enable in Settings > Developer, choose preset or custom loss/latency.

Charles proxy – configure iPhone Wi‑Fi HTTP proxy to the computer running Charles, then use Throttle Settings to simulate 2G/3G/slow networks.

Typical throttling parameters: GMS 14.4 KB/s, GPRS 40‑80 KB/s, EDGE 118‑237 KB/s, 3G 128‑1920 KB/s, HSDPA 348‑14400 KB/s.

Network Activity Monitoring

Use Instruments > Blank > Net Activity to observe request timing, data usage, and potential battery impact.

Energy Usage

Instruments' Energy Usage library reveals which threads consume the most power. Add the library via the Instruments Library panel and start profiling.

The guide concludes that fast startup, smooth UI, and efficient resource usage are critical for app success in a competitive market.