Evaluate dynamic vs. static cache invariant node number #54
Labels
No labels
ActivityPub
advanced features
basic functionality
bug
DHT
evaluation
refactoring
security
test case
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: schmittlauch/Hash2Pub#54
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
According to the Epichord tech report paper (page 4), the minimum number of nodes per cache slice is calculated depending on the total number of node probes and timed-out node probes.
For the sake of simplicity and avoiding another global counter needing to be synchronised, the first implementation will just use a static number of nodes for that cache invariance.
Once the software runs under real-world conditions, it might be worth evaluating the role of node time-outs for cache lookups and reconsider that decision.