ChronoSync

07/11/2017

11:13 AM Bug #4179: ChronoSync performs better without an exclude mechanism as publishing frequency increases

After discussion on NFD call (07/10/17), Alex suggested that bug is that ChronoSync should not process exclude intere... Ashlesh Gawande

07/10/2017

01:52 PM Bug #4179: ChronoSync performs better without an exclude mechanism as publishing frequency increases

With exclude: https://redmine.named-data.net/attachments/751/dfd.png
With no exclude: https://redmine.named-data.net... Ashlesh Gawande

07:53 AM Bug #4179 (Closed): ChronoSync performs better without an exclude mechanism as publishing frequency increases

With exclude mechanism, the performance seems worse with 5 nodes and an update rate of 13/second on average across th... Ashlesh Gawande

06/21/2017

01:13 PM Task #4090 (Code review): Urgent bugs caused by ndn-cxx change 3547

Ashlesh Gawande

01:12 PM Feature #4032 (Closed): Allow applications to set sequence number

Ashlesh Gawande

01:12 PM Bug #3990 (Closed): ERROR: Interest size exceeds maximum limit on exclude interest for large topologies

Ashlesh Gawande

06/19/2017

02:36 PM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet

Protobuf is out of question, as it doesn't solve the problem. My rough calculation (assuming 50 bytes names + seqnos... Alex Afanasyev

02:31 PM Bug #4140 (Closed): ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet

In ChronoSync a recovery interest triggers other side to send the full state.
ChronoSync can also send the full stat... Ashlesh Gawande