Re: C# DQPublisher Manager
Frank Quinn <fquinn.ni@...>
toggle quoted messageShow quoted text
2. Performance is pretty much the same with the broker as it is point to point
1. Logging doesn't need to be disabled - seems to work regardless.
So I tried with Proton 0.7 on linux (Fedora 22) and I can see:
Hi Mathias,I just tried an equivalent test with Qpid Broker 0.32 and proton 0.9.1 (with a few small changes to let it compile as proton changed their interface again) and the producer keeps crashing... so we'll get back to what's going on there later.
3. CPU is spread across several cores
4. Latency is around 4ms at data rates of around 10,000 msg/s
If you're getting latencies in the 2 second region, my first guess is that you're queuing in your client, have you tried printing out the queue size in your application? This is all finger in the air stuff though because this is all running on my local laptop.
When you're operating point to point, the producer is essentially throttled by the speed of the consumer. When a broker is involved, this relationship is effectively decoupled, so you may find that the producer is actually publishing faster than you expect now (enqueuing for sending is not the same as actually sending). That or else your applications haven't been compiled with multithreading support and they're all just fighting with each other for scheduler time. I'll try a windows test when I get a chance to see if I can replicate what you're seeing.
What sort of data rates and message sizes were you putting through?
On Tue, Jun 16, 2015 at 4:31 PM, Mathias Kim <Mathias.Kim@...> wrote: