[NMS-10459] Meassure and improve performance of Interface loading and mapping - The OpenNMS Issue Tracker

XML

Word

Printable

Details

Type: Sub-task
Status: Resolved (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 23.0.2, Meridian-2018.1.4, 24.0.0
Component/s: None
Security Level: Default (Default Security Scheme)
Labels:
None

Sprint:
Horizon - September 26 2018, Horizon - October 3rd 2018, Horizon - October 10th 2018, Horizon - October 17th 2018, Horizon - October 24th 2018, Horizon - October 31st 2018, Horizon - November 14th 2018, Horizon - November 21th 2018, Horizon - November 28th 2018, Horizon - December 5th 2018, Horizon - December 12th 2018

Description

A potential bottleneck is when there are cases where there are a lot of IP and/or SNMP interfaces.

The following code blocks:
https://github.com/OpenNMS/opennms/blob/240444e85630249e28290e931a47368e2e2b3cd3/features/topology-map/plugins/org.opennms.features.topology.plugins.topo.linkd/src/main/java/org/opennms/features/topology/plugins/topo/linkd/internal/LinkdTopologyProvider.java#L863

https://github.com/OpenNMS/opennms/blob/240444e85630249e28290e931a47368e2e2b3cd3/features/topology-map/plugins/org.opennms.features.topology.plugins.topo.linkd/src/main/java/org/opennms/features/topology/plugins/topo/linkd/internal/LinkdTopologyProvider.java#L889

might be slow if the dao calls return a lot of objects

Step 1: enhance Topology Generator to be able to generate interfaces: https://github.com/opennms-forge/opennms-topology-generator
Step 2: measure potential bottleneck
Step 3: evaluate and discuss possible solutions if needed
Step 4: implement improvement

Attachments

Activity

People

Assignee:

Patrick Schweizer

Reporter:

Patrick Schweizer

Votes:

0 Vote for this issue

Watchers:

3 Start watching this issue

Dates

Created:

19/Nov/18 10:01 PM

Updated:

16/Dec/18 3:51 AM

Resolved:

16/Dec/18 3:51 AM