Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Optimizing React Choropleth Map Rendering

DZone's Guide to

Optimizing React Choropleth Map Rendering

You can use smart React coding to massively speed up specialized map rendering by reducing polygons.

· Web Dev Zone
Free Resource

Start coding today to experience the powerful engine that drives data application’s development, brought to you in partnership with Qlik.

This is a Livecoding Recap – an almost-weekly post about interesting things discovered while livecoding. Always under 500 words and with pictures. You can follow my channel here. New streams almost every Sunday at 2 p.m. PDT. There’s live chat, come say hi!

Yesterday was supposed to be all about cutting up a large-ish codebase into small chunks that are easier to explain step-by-step. It was a great plan, but it didn’t quite happen.

Instead of doing that, I went down the rabbit hole of optimizing the choropleth map from Livecoding 24. Turns out my H1B visualization wasn’t slow because the dataset was big. It was slow because the map re-renders 3,220 county polygons on every update.

Let me explain.

We started with this:

unoptimized-rendering


See how it takes 2 or 3 seconds to react when you click a button? That’s bad.

And we finished with this:

optimized-rendering


Takes just a second. Still slow, but a lot better. The dataset to crunch is big, after all. 

Unfortunately, the paint flashing isn’t useful to show you what’s fixed. Looks like a parent component repaints and flashes everything. This is unfortunate and a potential clue for further improvements.

To make this 50% to 66% speed improvement, we did two things:

  1. Added shouldComponentUpdate to the County component.
  2. Avoided doing _.find to find data on every polygon draw.

I don’t know which improvement had a bigger effect, but when you _.find in a N=290 array 3,220 times, that’s 933,800 function calls that you’re making. Oops.

We fixed that by building a map beforehand. Like this:

const countyValueMap = _.fromPairs(
    this.props.values.map(d => [d.countyID, d.value]));


Then rendering County components in a loop, like this:

{counties.map((feature) => (

))}


That value prop used to be _.find(counties, {countyID: feature.id}), and that was dumb.

Lesson learned. Big-O matters even when you’re just doing JavaScript.

Inside County, we added shouldComponentUpdate. I don’t know why React wasn’t able to optimize this for us, but it wasn’t. Maybe because we were passing props in as functions? Probably.

The new County component looks like this:

class County extends Component {
    shouldComponentUpdate(nextProps, nextState) {
        const { zoom, value } = this.props;

        return zoom !== nextProps.zoom
            || value !== nextProps.value;
    }

        render() {
            // body from previous functional stateless version
        }
}


We know for a fact that a county polygon only has to re-render when the map’s zoom level changes or the value we’re displaying changes. That enables the map to change size and the value to change polygon colors.

Excellent. Many lessons learned.

You can see the code for React + D3 choropleth maps on Github. It’s embedded in a larger project, so there’s some context-specific stuff, but the component itself is made to be pretty general.

Create data driven applications in Qlik’s free and easy to use coding environment, brought to you in partnership with Qlik.

Topics:
react ,javascript ,tutorial ,map rendering ,polygons

Published at DZone with permission of Swizec Teller, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}