How Pinterest Cut Android Testing CI Build Times by 36%+
Runtime-aware sharding + EC2 bare-metal emulators reduced slowest shard 55% and E2E build time
Showing 12 of 12 articles (Page 1 of 1)
Runtime-aware sharding + EC2 bare-metal emulators reduced slowest shard 55% and E2E build time
Suppose you just saw an interesting rise or drop in one of your key metrics. Why did that happen? It’s an easy question to ask, but much harder to answer.
At Pinterest, our mobile infrastructure is core to delivering a high-quality experience for our users. In this blog, I’ll showcase how the Pinterest Mobile Builds team is leveraging Honeycomb.
Pinterest smooths out their Android video player for better playback.
Pinterest uses LMDB to optimize memory and speed up their API service.
Pinterest shares four big lessons from making their Android app faster.
Pinterest digs into how they make sure their app performance numbers are rock-solid and reliable.
Pinterest chopped their iOS app size by over 30%, using clever resource tricks and code cleanup.
Pinterest uses Honeycomb to keep their CI clear, stable, and easy to watch.
Pinterest revamped their CI system, splitting tasks and streamlining to cut build times by over half.
Pinterest started testing UI before code gets merged, catching bugs early to keep things steady.
Pinterest found a single tweak that slashed their build times by a jaw-dropping 99%.