Project

General

Profile

Actions

Bug #4291

closed

ndncatchunks: Reduce initial timeout of iterative version discovery

Added by Anonymous over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

100%

Estimated time:

Description

The current version discovery uses a timeout (interest lifetime) of 4 seconds.

Every time you run the application, you need to wait for at least one timeout (default:2). Thus gathering a file takes at least 4 seconds (by default 8 seconds), even if the file contains only one chunk. This makes the iterative version discovery rather unusable.

My suggestion:

  • Reduce the default timeout to 100ms.
  • Provide a parameter to raise it, if necessary.
  • Reduce timeouts for version discovery from 2 to 1.

This initial timeout will not affect the later RTO, given by '--aimd-rto-min' and '--aimd-rto-max'.


Related issues 1 (0 open1 closed)

Related to ndn-tools - Feature #3793: ndncatchunks version discovery: don't rely on timeoutsClosed

Actions
Actions #1

Updated by Anonymous over 6 years ago

Here's a log of the two default timeouts for the version discovery:

klaus@klaus-Latitude-E7470:~$ ndncatchunks -v /test > /dev/null
Data: Name: /test/%FD%00%00%01%5E%8C%3AJ%1D/%00%00
MetaInfo: ContentType: 0, FreshnessPeriod: 10000 milliseconds, FinalBlockId: %00%5D
Content: (size: 4400)
Signature: (type: SignatureSha256WithRsa, value_length: 256)

Discovered version = 1505591183901
Timeout for Interest /test?ndn.MinSuffixComponents=3&ndn.MaxSuffixComponents=3&ndn.ChildSelector=1&ndn.InterestLifetime=100&ndn.Nonce=2776025280&ndn.Exclude=*,%FD%00%00%01%5E%8C%3AJ%1D
Timeout for Interest /test?ndn.MinSuffixComponents=3&ndn.MaxSuffixComponents=3&ndn.ChildSelector=1&ndn.InterestLifetime=100&ndn.Nonce=1921851405&ndn.Exclude=*,%FD%00%00%01%5E%8C%3AJ%1D
Found data with the latest version: 1505591183901

(it already includes the change of the Interest lifetime to 100ms)

Actions #2

Updated by Davide Pesavento over 6 years ago

This is a duplicate of #3793

Actions #3

Updated by Anonymous over 6 years ago

It's more like a quick fix for #3793, because I couldn't figure out how to avoid timeouts completely.

Actions #4

Updated by Anonymous over 6 years ago

  • Related to Feature #3793: ndncatchunks version discovery: don't rely on timeouts added
Actions #5

Updated by Junxiao Shi over 6 years ago

I agree with the idea in general.

100ms is too small. A round-trip from Asia to Norh America is more than 200ms. 300ms is acceptable to me.

Actions #6

Updated by Anonymous over 6 years ago

Makes sense, let's do 300ms.

Actions #7

Updated by Anonymous over 6 years ago

  • Status changed from New to Code review
Actions #8

Updated by Anonymous over 6 years ago

  • Description updated (diff)
Actions #9

Updated by Anonymous over 6 years ago

  • Status changed from Code review to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF