You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the mixer uses the async executor to schedule the packet mixing. A better, more efficient approach is needed, that would in ideal case use a common buffer for outgoing and forwarded packets.
Such a buffer could be used for generating also the looping traffic (e.g. probing path observing), junk traffic (to increase the ambiguity of packet sending for low throughput state of the network) and real mixed packets.
Combining multiple sources and increasing throughput however strains the executor. A better approach would be to use the desired distribution on the output and use tick based sampling in discrete time instances to extract the desired number of packets from an easily poppable buffer.
Description
None
Relevant issues
None
Definition of DONE
The mixer working efficiently over:
a common buffer
using the executor only for single discrete time based wakeups
Currently the mixer uses the async executor to schedule the packet mixing. A better, more efficient approach is needed, that would in ideal case use a common buffer for outgoing and forwarded packets.
Such a buffer could be used for generating also the looping traffic (e.g. probing path observing), junk traffic (to increase the ambiguity of packet sending for low throughput state of the network) and real mixed packets.
Combining multiple sources and increasing throughput however strains the executor. A better approach would be to use the desired distribution on the output and use tick based sampling in discrete time instances to extract the desired number of packets from an easily poppable buffer.
Description
None
Relevant issues
None
Definition of DONE
The mixer working efficiently over:
The text was updated successfully, but these errors were encountered: