Hello Gordon, On Mon, 2013-04-29 at 13:49 +0100, Gordon Sim wrote: > On 04/29/2013 05:17 AM, Robert Seward wrote: > > A couple comments on the whole thing. > > > > The persistence is really slow on Fedora 18 with QPID 0.20. How ever the > > persistence is reasonable (if not slower than I would like) on Centos > > 6.3. QPID 0.14. > > Can you describe the pattern and the results you are seeing?
Sorry. I was pulled off the project for a bit and missed your e-mail. The project is using QPID as a web crawler. On my laptop 8 core Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz with 12 GB of memory. qpid-0.20 with persistence enabled only allows approximately 10 messages to be queued (persisted) per second. The server running QPID 0.14 persists approximately 740 messages per second. 24 core AMD Opteron(TM) Processor 6234 with 32 GB of memory. Running other Messaging brokers ActiveMQ and RabbitMQ with this web crawling software, my laptop and the server have a much closer parity when it comes to queuing (persisting) messages. Let me know if I can provide more detailed information to identify the issue. It could be configuration on my QPID 0.20 laptop? As far as I remember the configuration on QPID 0.14 and QPID 0.20 is as identical as possible. It could be the difference between QPID 0.20 and QPID 0.14? I hope not as this means QPID is regressing performance wise. Thank you, Rob > > > Although the persistent queues and messages work in 0.20. flow-to-disk > > limit policy is not recognized. flow-to-disk policy is ignored with a > > warning message when QPID starts. I gather from this URL this is a known > > problem. > > > > - https://issues.apache.org/jira/browse/QPID-4339 > > That's right, the flow to disk policy was removed in 0.20 as it was not > very effective. I have an alternative in review at present - > https://issues.apache.org/jira/browse/QPID-4339 - and plan to have that > on trunk shortly (it will be part of the 0.24 release). > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
