Hi
I got an average of 25 seconds in the request for "create" messages and 22 for
"delete" messages (this time does not contains the time of building the message
just the send) and 2 seconds in the response, both of them. I found out the
best performance was with the send.setCapacity(-1) option enabled. Also tried
with {link: {reliability: unreliable}} in the address but haven't got better
results.
The broker was our not being used or in low usage, it's a dedicated server that
only my team uses. No other tests where being done.
Best,
Filipe Santos
-----Original Message-----
From: Gordon Sim [mailto:[email protected]]
Sent: sexta-feira, 8 de Agosto de 2014 17:04
To: [email protected]
Subject: Re: Bulk binding
On 08/08/2014 04:57 PM, Filipe Santos wrote:
> I'm doing exactly what you suggested and also threading my requests in order
> to take advantage of the local cpu, but I'm always eager to improve
> benchmarks.
How long is it taking doing all the requests asynchronously?
On the fetch() side you have a non-zero capacity on your receiver? Is there
anything else going on on the broker while you are binding? E.g.
publishing to the exchange to which the bindings are being established?
Binding hasn't been considered critical path, so its not the most optimised
path. If the issue is simply how quickly the broker can establish the bindings,
then it may not help to merge them all into one message anyway.
---------------------------------------------------------------------
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]
