...@gmail.comwrote:
2012/8/29 Julie Anderson julie.anderson...@gmail.com:
I understand your frustration. I don't put the code here because I don't
want to, but because I am legally unable to. If you have a boss or
employer
you can understand that. :) I will try to come up with a simple version
Just tested ZeroMQ and Java NIO in the same machine.
The results:
*
- ZeroMQ:*
message size: 13 [B]
roundtrip count: 10
average latency: *19.620* [us] *== ONE-WAY LATENCY*
*- Java NIO Selector:* (EPoll)
Average RTT (round-trip time) latency of a 13-byte message: 15.342 [us]
Min Time:
and writing to
the network)
-Julie
On Wed, Aug 29, 2012 at 10:24 AM, Chuck Remes li...@chuckremes.com wrote:
On Aug 29, 2012, at 10:13 AM, Julie Anderson wrote:
Just tested ZeroMQ and Java NIO in the same machine.
The results:
*
- ZeroMQ:*
message size: 13 [B]
roundtrip count: 10
average
OWT: (one-way time)
Iterations: 2,221,118 | Avg Time: *5095.66 nanos* | Min Time: 4220 nanos |
Max Time: 135584 nanos | 75%: 5001 nanos | 90%: 5037 nanos | 99%: 5071
nanos | 99.999%: 5094 nanos
-Julie
On Wed, Aug 29, 2012 at 12:18 PM, Julie Anderson
julie.anderson...@gmail.com wrote:
New
See my comments below:
On Wed, Aug 29, 2012 at 4:06 PM, Robert G. Jakabosky
bo...@sharedrealm.comwrote:
On Wednesday 29, Julie Anderson wrote:
So questions remain:
1) What does ZeroMQ do under the rood that justifies so many extra clock
cycles? (I am really curious to know)
ZeroMQ
See my comments below:
On Wed, Aug 29, 2012 at 5:28 PM, Chuck Remes li...@chuckremes.com wrote:
On Aug 29, 2012, at 4:46 PM, Julie Anderson wrote:
See my comments below:
And mine too.
On Wed, Aug 29, 2012 at 4:06 PM, Robert G. Jakabosky
bo...@sharedrealm.com wrote:
On Wednesday 29
See my comments below:
They appear to
be single threaded synchronous tests which seems very unlike the kinds
of applications being discussed (esp. if you're using NIO). More
realistic is a network connection getting slammed with lots of
concurrent sends and recvswhich is where lots of
Over 10GbE ZeroMQ claims a latency of 33 micros from
end-to-endhttp://www.zeromq.org/results:10gbe-tests-v031.
If you subtract 2 micros from over-the-wire transit time it is still 31
micros. That's a lot!
But if you make a simple test sending one packet from one side to the
other, the total time
I sent an email earlier titled: Java NIO Selector Minimum Possible
Latency.
I am NOT doing anything fancy like kernel bypass.
On Tue, Aug 28, 2012 at 8:17 PM, Steven McCoy steven.mc...@miru.hk wrote:
On 28 August 2012 20:11, Julie Anderson julie.anderson...@gmail.comwrote:
Over 10GbE ZeroMQ
Thanks, Ian. But I am more interested in the results that ZeroMQ has
accomplished. Has anyone from ZeroMQ run any test on loopback that can
share some results?
-J
On Fri, Aug 24, 2012 at 3:57 PM, Ian Barber ian.bar...@gmail.com wrote:
On Fri, Aug 24, 2012 at 5:20 PM, Julie Anderson
PM, Julie Anderson
julie.anderson...@gmail.com wrote:
Hi,
Java NIO UDP benchmark results snipped
So my questions for the community are:
1 - Is my minimum time of 13 micros with average of 19 micros optimum for
this round trip packet test. It looks like I am beating ZeroMQ by far
Hi,
I am comparing ZeroMQ latencies with the ones from our current system.
From my system benchmarks I was able to get a round trip time as low as 8
micros with an average of 10 micros on loopback (127.0.0.1).
I see from this paper http://www.zeromq.org/results:10gbe-tests-v031 that
ZeroMQ has
Hi,
I am doing some benchmarks with an optimized Java NIO selector on Linux
over loopback (127.0.0.1).
My test is very simple:
- One program sends an UDP packet to another program that echoes it back to
the sender and the round trip time is computed. The next packet is only
sent when the
13 matches
Mail list logo
