Geomap is insanely slow after migration to Graphite in NAV 4.0

Bug #1403797 reported by Morten Brekkevold
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Network Administration Visualized
Fix Released
High
Morten Brekkevold

Bug Description

Due to the way Geomap handles fetching of load metrics (at the last minute), it became insanely inefficient after the transition from local RRD files to the service-based graphite-web.

Each metric is currently retrieved in a separate HTTP request to graphite-web, which translates to massive overhead.

The Geomap load fetching code should be refactored to discover, at an earlier stage, which load metrics are needed, and fetch these in bulk from graphite-web.

Revision history for this message
Morten Brekkevold (mbrekkevold) wrote :

fix here: https://nav.uninett.no/hg/stable/rev/3f7bdfc1905e

There are still some improvements that could be made, like picking data only from one of the link partners per link.

Changed in nav:
milestone: none → 4.2.2
status: In Progress → Fix Committed
Changed in nav:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.