I added that and didn't see any noticable difference. My test was a single
producer that produces messages as fast as it can and one consumer in
pubsub. I changed my connect/session creation from this
self.conn = Connection(sock=sock)
self.conn.start(timeout=10)
self.session = self.conn.session(str(uuid4()))
to this
self.conn = Connection(sock=sock)
self.conn.start(timeout=10)
self.session = self.conn.session(str(uuid4()))
self.session..auto_sync = False
Perhaps I am missing something else where...
On Thu, Dec 10, 2009 at 2:22 AM, Gordon Sim <[email protected]> wrote:
> On 12/10/2009 05:37 AM, Glen Marchesani wrote:
>
>> One interesting note is the performance of our python client was around
>> 1000
>> msgs/second. With the java client we are seeing something closer to
>> 10,000
>> msgs/second.
>>
>
> Were you using synchronous transfer with python? That is the default for
> python; you can switch to asynchronous by setting session.auto_sync = False
> and then explicitly sync() as needed.
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>
>
