View Issue Details

IDProjectCategoryView StatusLast Update
0005550GNUnettransport servicepublic2021-04-05 11:25
ReporterChristian Grothoff Assigned Tot3sserakt  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product VersionGit master 
Target Version0.14.1Fixed in Version0.14.1 
Summary0005550: [TNG] backchannel support
DescriptionThe UDP plugin will attempt to transmit messages via the so-called backchannel feature (GNUNET_TRANSPORT_communicator_notify()). While in 0005547 the test should just drop backchannel data, for this version of the test the test driver should pass backchannel data to the other peer (GNUNET_TRANSPORT_CommunicatorNotify()).

Performance (goodput, latency) should be measured as before.

This variant of the test should also use the same basic C code, with the backchannel feature being controlled by a simple testcase driver option in the configuration file (i.e. [communicator-test] ENABLE_BACKCHANNEL = YES/NO).
Tagstng

Relationships

related to 0006011 assignedt3sserakt [TNG] UNIX communicator performance issues 
related to 0006098 assignedt3sserakt [TNG] UDP communicator performance issues 
child of 0005710 confirmed TNG meta issue 

Activities

schanzen

2019-12-31 05:29

manager   ~0015230

This issue is blocked by 0006011 as the UDP communicator is too slow to pass any test, with or without backchannels.
It can still be implemented, though, just expect the test to fail anyway.

schanzen

2019-12-31 06:45

manager   ~0015231

Implemented in 658ba3f2b..65b645e3c.
Not sure if the backchannel ACK is doing what it is supposed to do yet...

schanzen

2020-01-01 05:39

manager   ~0015232

MQ is so clogged from transport -> UDP communicator from sending messages that backchannel ACK is not coming through (timely).
Can be tested by delaying the short test scheduling by 1s each.

Still unclear of ACKs are correctly processed.

schanzen

2020-06-01 19:16

manager   ~0016219

Backchannel signalling seems to work now. However, I get around 10% package loss (and hence a failed test) with backchannel.
No backchannel works fine for UDP.
Consequently, this is likely a ratcheting issue.

Christian Grothoff

2020-06-01 22:05

manager   ~0016221

Just curious: 10% loss for the backchannel, or 10% loss overall?

schanzen

2020-06-01 22:08

manager   ~0016222

10% overall. The backchannel does not loose messages, but they are processed with high delay.
Presumably for the same reason why performance in tests is bad (scheduling in single process).

schanzen

2021-04-05 11:25

manager   ~0017686

0.14.1 released

Issue History

Date Modified Username Field Change
2019-02-08 19:06 Christian Grothoff New Issue
2019-02-08 19:06 Christian Grothoff Status new => assigned
2019-02-08 19:06 Christian Grothoff Assigned To => ch3
2019-02-12 09:22 Christian Grothoff Target Version => 0.12.0
2019-05-02 14:41 Christian Grothoff Relationship added child of 0005710
2019-05-03 18:54 Christian Grothoff Assigned To ch3 =>
2019-05-03 18:54 Christian Grothoff Status assigned => confirmed
2019-11-16 18:41 Christian Grothoff Target Version 0.12.0 => 0.13.0
2019-12-21 23:34 schanzen Assigned To => schanzen
2019-12-21 23:34 schanzen Status confirmed => assigned
2019-12-31 05:29 schanzen Note Added: 0015230
2019-12-31 05:29 schanzen Relationship added related to 0006011
2019-12-31 06:45 schanzen Note Added: 0015231
2020-01-01 05:39 schanzen Note Added: 0015232
2020-04-22 17:22 schanzen Target Version 0.13.0 => 0.14.0
2020-05-10 08:32 schanzen Assigned To schanzen =>
2020-06-01 00:49 Adminknox Issue cloned: 0006287
2020-06-01 19:16 schanzen Note Added: 0016219
2020-06-01 19:21 schanzen Summary backchannel support => [TNG] backchannel support
2020-06-01 22:05 Christian Grothoff Note Added: 0016221
2020-06-01 22:08 schanzen Note Added: 0016222
2020-06-01 22:22 schanzen Relationship added related to 0006098
2020-08-14 12:01 schanzen Tag Attached: tng
2020-09-21 15:16 t3sserakt Assigned To => t3sserakt
2020-10-28 13:06 schanzen Target Version 0.14.0 => 0.15.0
2020-12-14 11:44 t3sserakt Status assigned => resolved
2020-12-14 11:44 t3sserakt Resolution open => fixed
2020-12-14 11:44 t3sserakt Fixed in Version => Git master
2021-02-21 11:04 schanzen Fixed in Version Git master => 0.14.1
2021-02-21 11:05 schanzen Target Version 0.15.0 => 0.14.1
2021-04-05 11:25 schanzen Note Added: 0017686
2021-04-05 11:25 schanzen Status resolved => closed