Re: C# DQPublisher Manager
I tested the broker on a Fedora Virtualbox and the results were much better than on my Windows version. The performance was as good as with point to point for capturereplayc/mamalistenc (5 Symbols) and our C# classes.
For testing the C# classes I was simulating orderbooks. In the end I was sending an average of 14 messages per second. Each message contained on average 25 fields.
The same test with a Windows broker led to huge delay. Since the amount of data is fairly low, something must have gone wrong when compiling qpid under Windows.
Interestingly, also under Fedora I have to add the –t parameter. Without, no communication happens.
Unfortunately, with Virtualbox/Fedora our C# publisher and listener experience some problems since not every subscription is successful. In about 50% of the cases I get this behavior:
- Publisher connects successfully to qpid broker
- Listener connects successfully to qpid broker and submits desired symbol
- Symbol arrives at publisher, publisher starts sending data to qpid broker
- Qpid broker receives data (as I can see on the output) but never forwards to the listener
Monitoring the port shows that no messages ever arrive at the machine the listener is running on.
No similar behavior with capturereplayc/mamalistenc. Also, no similar issues with qpid under Windows.
Did you test the qpid broker/openmama combo with a C# Listener yet?
From: Frank Quinn [mailto:fquinn.ni@...]
Sent: Montag, 22. Juni 2015 17:40
To: Mathias Kim
Subject: Re: [Openmama-dev] C# DQPublisher Manager
I was only testing with producer / consumer which is only one symbol so perhaps that's part of the issue here. I'll test with more symbols too when I get back to my machine. What sort of data rates were you running at?
On Mon, Jun 22, 2015 at 4:25 PM, Mathias Kim <Mathias.Kim@...> wrote: