[CONTROLLER-1720] Improve RangeSet tracking performance Created: 13/Jun/17  Updated: 25/Jul/23  Resolved: 06/Nov/21

Status: Resolved
Project: controller
Component/s: clustering
Affects Version/s: None
Fix Version/s: 3.0.13, 4.0.6, 2.0.10

Type: Improvement
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Relates
relates to CONTROLLER-2011 Do not use RangeSet in serialization Resolved

 Description   

We are currently using a RangeSet to track various identifiers in the FE/BE conversation. These identifiers are UnsignedLongs, hence come from a discrete set. Unfortunately default TreeRangeSet is designed to work in continuum, forcing us to use half-closed ranges, as evidenced https://git.opendaylight.org/gerrit/58800.

This is not really efficient as we could do better with a dedicated discrete RangeSet implementation. Explore our options and come up with a better solution.

Note this does not have to impact serialization format, as we can still translate to/from normal RangeSets.


Generated at Wed Feb 07 19:56:17 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.