View Issue Details

IDProjectCategoryView StatusLast Update
0006011GNUnetUNIX transportpublic2020-02-18 17:15
ReporterschanzenAssigned Toschanzen 
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
Product Version 
Target Version0.13.0Fixed in Version 
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
TagsNo tags attached.

Relationships

related to 0005550 assignedschanzen backchannel support 
child of 0005710 confirmed TNG meta issue 

Activities

schanzen

2019-12-26 06:20

manager   ~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

manager   ~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

manager   ~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

manager   ~0015377

Last edited: 2020-02-18 17:14

View 2 revisions

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

manager   ~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 View Revisions
2020-02-18 17:15 schanzen Note Added: 0015378