New Charting Engine

Welcome to Grow's newest charting engine!


We just finished a large charting upgrade, switching to the newest version of our charting engine. While there are a lot of things to be excited about, here's a few of our favorite reasons we made this update:

Update Reasons

Better chart visuals

The new version of the charting engine has better, clearer visuals all the while opening things up for us to be able to potentially add some new chart types down the road!

Old Engine Support had ended

The old charting engine is no longer supported. That means there would be no further bug fixes or enhancements and if we hit any problems we were on our own. The new charting engine has full support for our developers which ultimately allows us to support you, our customers, better.

Lots of bug fixes in new version

Because the old engine was getting a bit old, it had a handful of annoying visual glitches and issues. These are all fixed by transitioning to the new charting engine.

Differences between the Charting Engines

While the two engines are very similar, there are a few differences in how they look and work.

Visual Differences

Most of the visual differences you will see should be positive. Legends and tooltips are now color coordinated to their data series, making it much easier to read your data. Lines are crisper and text should be more readable at various sizes.

Loading Differences

The biggest difference you may notice is in how the New Engine loads charts.

The Old Engine would try to load everything at once as fast as possible. It would suck up all the available computer processor power and memory and it would lock up your browser until it had finished loading. Imagine a hoard of hungry teenagers rushing the buffet line, it might be quick but it is messy.

Our partner behind the charting engine decided that for the New Engine, they would load things in a smarter, nicer way, and not thrash your browser. However, that does mean that some dashboards will load a bit more slowly.

If you do notice a dashboard running slower, one of the best ways to reduce loading time is to reduce the number of metrics on that dashboard.

We suggest a max of 20-25 metrics per dashboard for optimal performance.

Was this article helpful?