Actions
Task #3862
open
Investigate unordered CS
Status:
New
Priority:
Normal
Assignee:
-
Category:
Tables
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Description
Investigate ContentStore implementation based on unordered container.
CS is a major bottleneck of forwarding performance, as shown in benchmarks. It's believed that CS is slow because it uses an ordered container.
Note that CS must still support Interest name being a prefix of Data name for Interests with CanBePrefix element, and cannot require exact matching only.
Possible data structures include but are not limited: tree, hashtable, Bloom filters.
Updated by
Actions