Project

General

Profile

Actions

Feature #1301

open

Shrink table size during memory stress

Added by Junxiao Shi about 10 years ago. Updated about 6 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Tables
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Watch for nfd process memory usage. When memory usage is higher than a configurable threshold, shrink table size to avoid crash.

  1. shrink ContentStore
  2. delete/aggregate Measurements entries
  3. stop accepting new PIT entries (drop Interests)

Related issues 4 (2 open2 closed)

Related to NFD - Task #1623: Make ContentStore size configurableClosed

Actions
Related to NFD - Bug #4499: Unbounded queuing in StreamTransportNew

Actions
Has duplicate NFD - Feature #4070: Replacement policies for PIT (Pending Interest Table)Duplicate

Actions
Is duplicate of NFD - Feature #5060: Congestion Detection: Monitor size of PIT vs. available memoryNew

Actions
Actions #1

Updated by Junxiao Shi almost 10 years ago

Limiting memory usage is a useful feature for deployment in OpenVZ container.

NFD in my box is crashing every day due to memory exhaustion.

Actions #2

Updated by Junxiao Shi almost 10 years ago

  • Target version deleted (v0.2)

20140517 conference call decides this task is too complex to deliver in v0.2.

The immediate problem can be solved with Task #1623, which is a subset of this task.

Actions #3

Updated by Junxiao Shi almost 10 years ago

  • Related to Task #1623: Make ContentStore size configurable added
Actions #4

Updated by Lan Wang about 9 years ago

  • Assignee set to Minsheng Zhang
Actions #5

Updated by Junxiao Shi almost 7 years ago

  • Has duplicate Feature #4070: Replacement policies for PIT (Pending Interest Table) added
Actions #6

Updated by Junxiao Shi almost 7 years ago

  • Tracker changed from Task to Feature
  • Assignee deleted (Minsheng Zhang)
Actions #7

Updated by Junxiao Shi almost 7 years ago

On the Readiness of NDN for a Secure Deployment: The Case of Pending Interest Table has a benchmark on how many PIT entries would cause NFD 0.4.0 to crash. Their findings indicate that, using names with 256 name components, NFD uses up 8GB of memory with about 2200 PIT entries.

Actions #8

Updated by Davide Pesavento about 6 years ago

  • Related to Bug #4499: Unbounded queuing in StreamTransport added
Actions #9

Updated by Davide Pesavento about 6 years ago

  • Priority changed from Normal to Low
Actions #10

Updated by Junxiao Shi over 4 years ago

  • Is duplicate of Feature #5060: Congestion Detection: Monitor size of PIT vs. available memory added
Actions

Also available in: Atom PDF