| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
| |
The problem was I was basically flushing twice for every message when
doing request reply.
This gives the sender the opportunity to finish writing a full message
to the queue, which we then check for before flushing.
This makes request reply latency benchmarks go down from like 90ms to
200us.
|
| | |
|
| |
|
|
|
| |
fixed issue where not all data was being sent
request reply has a performance issue but technically works
|
| |
|
|
| |
Seems to not flush the last message
|
| | |
|
| |
|
|
| |
This makes things much easier to use as a library
|
|
|
Add a bunch of tests for the client
|
