View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006011GNUnetUNIX transportpublic2019-12-25 14:032024-03-15 09:56
Reporterschanzen Assigned Tot3sserakt  
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
Target Version0.21.2 
Summary0006011: [TNG] UNIX communicator performance issues
DescriptionA trained eye might notice the absolutely unacceptable, abysmal performance of this
communicator considering it is using UDS (we should expect ~XGB/s!).
As it is not meant to be used productively (and can't really) this is not a blocker, but
still something worth investigating. I do not know if this was also the case for the old
plugin
Tagstng

Relationships

related to 0005550 closedt3sserakt [TNG] backchannel support 
child of 0005710 confirmed TNG meta issue 

Activities

schanzen

2019-12-26 06:20

administrator   ~0015222

This is also an issue for the TCP communicator. Maybe this is a general issue with MQ or TNG api.

schanzen

2019-12-26 20:54

administrator   ~0015223

We now also have a UDP communicator which does no flow control (additional messages with (mock)transport).
It is now likely clear that something is wrong with the MQ (in general?).

schanzen

2020-02-11 17:51

administrator   ~0015347

For reference, current numbers:

* Size packet test done.
* 12798/12798 packets -- avg latency: 3148434 us
* Short size packet test done.
* 5000/5000 packets in 838528 us (745 KiB/s) -- avg latency: 409401 us
* Long size packet test done.
* 5000/5000 packets in 1717230 us (88 MiB/s) -- avg latency: 1034307 us

schanzen

2020-02-18 17:13

administrator   ~0015377

Last edited: 2020-02-18 17:14

 In HEAD performance is now increased drastically (but still not optimal).

Unix: Short ~5MB/s Long: ~300MB/s
TCP: Short ~4MB/s Long: ~200MB/s

UDP is currently not functional. The packet send logic is very inefficient and the test always fails.

schanzen

2020-02-18 17:15

administrator   ~0015378

Note that the issue might actually be test design and lack of FC and not so much the communicator itself.

Issue History

Date Modified Username Field Change
2019-12-25 14:03 schanzen New Issue
2019-12-25 14:03 schanzen Status new => assigned
2019-12-25 14:03 schanzen Assigned To => schanzen
2019-12-25 14:03 schanzen Relationship added child of 0005710
2019-12-26 06:20 schanzen Note Added: 0015222
2019-12-26 20:54 schanzen Note Added: 0015223
2019-12-31 05:29 schanzen Relationship added related to 0005550
2020-02-11 17:51 schanzen Note Added: 0015347
2020-02-18 17:13 schanzen Note Added: 0015377
2020-02-18 17:14 schanzen Note Edited: 0015377
2020-02-18 17:15 schanzen Note Added: 0015378
2020-04-22 17:22 schanzen Target Version 0.13.0 => 0.14.0
2020-05-10 08:31 schanzen Assigned To schanzen =>
2020-06-01 00:49 Adminknox Issue cloned: 0006288
2020-07-16 16:21 t3sserakt Assigned To => t3sserakt
2020-08-14 12:01 schanzen Tag Attached: tng
2020-10-28 13:06 schanzen Target Version 0.14.0 => 0.15.0
2021-06-10 19:36 schanzen Target Version 0.15.0 => 0.16.0
2021-12-31 09:29 schanzen Target Version 0.16.0 => 0.17.0
2021-12-31 09:32 schanzen Target Version 0.17.0 => 1.0.0
2024-03-07 20:31 schanzen Target Version 1.0.0 => 0.21.1
2024-03-15 09:56 schanzen Target Version 0.21.1 => 0.21.2