What profiling my Universal React-Redux app revealed

CPU profiling with Chrome Devtools

A little truth that not everybody knows is that you’re unlikely to know what happens in your application until you actually look at your application while it is running. It doesn’t matter if you are the developer that wrote most of the application code, todays applications might be so complex that what happens behind the scene is hard to picture.

A story that supports this statements happened a week ago, when I started looking into the code that performs the server side rendering of an application. “It’s straightforward and it works fine” I thought, “after all it’s less than one hundred lines”. But I was just guessing.
What I saw looking at the code was different from what I saw running the code with the proper investigation tools.

Long story short, this process allowed me to track a mistake I made that was hurting the application performance. Here is how I did it.

You can continue reading this post on my blog. Click here to continue.

--

--

--

Passionate software engineer, trail runner, traveler. Insanely affected by lifelong learning. @darioghilardi

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Dario Ghilardi

Dario Ghilardi

Passionate software engineer, trail runner, traveler. Insanely affected by lifelong learning. @darioghilardi

More from Medium

Make your development easier with version controlling and NoSQL

SANITY AS A BACKEND SERVICE

When your focus is fading…

Fixing “Error parsing triggers: Cannot find module ‘./logger’” in Firebase CLI