Feature #5060
open
Congestion Detection: Monitor size of PIT vs. available memory
0%
Description
The main idea here is to avoid overflowing the available memory for PIT entries, by proactively adding congestion marks once the PIT grows too large.
However, the exact algorithm is still work-in-progress. Feel free to discuss suggestions below.
Files
Updated by Junxiao Shi about 5 years ago
- Has duplicate Feature #1301: Shrink table size during memory stress added
Updated by Junxiao Shi about 5 years ago
- File PIT-full_20170301.docx PIT-full_20170301.docx added
I thought about this long ago. See notes in attachment.
The main design challenge is fairness. Using congestion marks some alleviates this challenge, if everybody is cooperating.
On implementation side: do you want to enforce a fixed PIT capacity limit, or read system RAM usage?
Updated by Davide Pesavento about 5 years ago
- Category set to Tables
- Start date deleted (
11/27/2019)
Updated by Anonymous about 5 years ago
Junxiao Shi wrote:
I thought about this long ago. See notes in attachment.
The main design challenge is fairness. Using congestion marks some alleviates this challenge, if everybody is cooperating.
Yeah, I wouldn't worry too much about it, and just leave fairness to the endpoints.
On implementation side: do you want to enforce a fixed PIT capacity limit, or read system RAM usage?
Not sure yet. I assume there has to be some sort of best practice how to deal with limited memory?
Fixed PIT limit is likely easier to implement.
Updated by Davide Pesavento 12 months ago
- Related to Feature #1624: Design and Implement Congestion Control added