Performance Optimization Techniques for Alipay Mini‑Games Runtime

Alipay’s seasonal mini‑game events attract millions of users, making performance a critical factor. The article explains how mini‑games are packaged, compiled with the Mini‑Program IDE, and run inside a unified container that manages download, initialization, and rendering.

The runtime operates on a single "Game Main Thread" where JavaScript, rendering, physics, and audio are processed synchronously, leading to potential frame drops when tasks exceed the 16 ms budget per frame.

Multithreading

To prevent long‑running JavaScript from blocking rendering, heavy calculations are offloaded to Worker threads. The performance gain equals the parallel speedup minus communication overhead; if communication cost exceeds computation time, no benefit is observed.

Benchmark using Cannon.js physics on an iPhone 12 shows frame rates improving from 5 fps to 55 fps when physics is moved to a Worker.

Independent Audio Thread

Game audio can involve 1‑20+ simultaneous sound effects, causing the main thread to stall. By decoupling audio via a proxy player and implementing a low‑latency OpenAL backend with dynamic task dropping, audio latency is kept under 30 ms and frame rates increase noticeably.

File System Optimization

Mini‑games perform over 100 file operations per second during loading, far exceeding typical Mini‑Program usage. Optimizations include a size‑management cache, lock‑free parallel writes/deletes via temporary staging areas, and a main‑document thread lock to ensure consistency.

Performance gains: writeFileSync 2.9×, copyFileSync 1.7×, readFileSync 3.8×, setStorageSync 19×.

Text Rendering Optimization

Custom fonts cause costly per‑character fallback rendering. A two‑level cache for characters and font styles reduces measurement and draw calls, yielding up to 40× faster fillText/strokeText and 26× faster measureText.

Independent Render Thread

Separating the Render phase into its own thread prevents long render tasks from blocking the Update phase. A producer‑consumer model with double‑buffered command queues reduces lock contention, and resource proxy objects avoid blocking the main thread for API calls that return values.

Testing with an aquarium demo shows a 20%+ increase in average FPS when the independent render thread is enabled.

iOS High‑Performance Mode

On iOS, JavaScriptCore cannot use JIT, causing 2‑5× slower execution. Replacing it with WKWebView (high‑performance mode) improves script speed but introduces serialization overhead. Optimizations include a binary serialization protocol, batched command payloads, and async‑ified synchronous calls.

Result: load time reduced from 8 s to 5 s, frame‑drop rate from 4.9% to 0.5%, and 27.8% lower energy consumption over 5 minutes.

Conclusion

Over the past year, Alipay’s mini‑game host has been optimized across I/O, execution environment, and rendering pipelines, delivering substantial performance gains, smoother gameplay, and lower power usage, while supporting rapid growth of the mini‑game ecosystem.