ipdevpoll CAM collection optimizations

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

Bug Description

As presented on the last nav-ref meeting. Using the generic "load-and-compare Django models" cycle for plugins in ipdevpoll causes this plugin to be a memory and I/O hog, as there are usually very large numbers of MAC addresses to processes. The addresses in themselves are quite small, so there is a lot of overhead we could get rid of here.

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

Some optimizations are ready for NAV 4.1, but these have only been tested on small data sets. The full effect is therefore not easily measureable, except for about 6MB of process memory saved when querying 66 devices.

fixes merged here: https://nav.uninett.no/hg/default/rev/0b2283d4ec83

Changed in nav:
status: New → In Progress
milestone: none → 4.1.0
assignee: nobody → Morten Brekkevold (mbrekkevold)
summary: - optimize ipdevpoll's cam plugin, it is currently an I/O and memory hog.
+ ipdevpoll CAM collection optimizations
Changed in nav:
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  Edit
Everyone can see this information.

Other bug subscribers