Late last year, the  Aha! Develop team added support for team line-level reporting. During a team demo in the run-up to the release, we discovered one of our internal sprint reports was taking 15 minutes to load, almost freezing the browser in the p

The RubyLA blog offers insights, tutorials, and community updates for Ruby developers in Los Angeles and beyond. Developers can explore Ruby language features, web development frameworks, and best practices for building Ruby applications. Additionally, the blog covers Ruby meetups, events, and job opportunities in the Los Angeles area, fostering collaboration and networking within the local Ruby community.

RUBYLAND

A frontend performance investigation at Aha! uncovered a sprint report taking 15 minutes to load due to a 1,000-day-long sprint. Profiling revealed two unexpected culprits: lodash's cloneDeep and moment.format, both called repeatedly in hot paths. The team built a benchmarking suite to validate hypotheses, refactored the data structure to skip empty days and reduce memory usage, and replaced the expensive utility calls with explicit, lightweight alternatives. The combined fix achieved a 100x+ performance improvement, reducing parse time from 15 minutes to a fraction of a second.

The importance of benchmarks

Our preferred solution: Combined approaches