I'd agree with Gordon. If at all possible I will pre-create my private queues, rather than creating them on demand. Writing a bit of extra code for working with a fix number of queues is worth from a performance standpoint.
Regards, Rajith On Mon, Jul 16, 2012 at 8:39 AM, Gordon Sim <[email protected]> wrote: > On 07/16/2012 12:34 PM, Toralf Lund wrote: >> >> Hi. >> >> What kind of overhead to you expect from having to create the >> ("private") queue when initialising a qpid::messaging::receiver? > > > If it is not a durable queue then the overhead is not that high, however... > > >> I'm implementing request-response type communication over a direct >> exchange, with a private "auto-delete" queue for responses (whose >> address is specified in replyTo on the request message.) So far, I've >> just created a new queue on every call rather than trying to keep the >> same one throughout the session because it's simpler in many ways - it >> saves me from some queue management, and I don't have to worry about >> reading the wrong response e.g. because of a time-out waiting for a >> reply to a previous request. >> >> So, do you think that this sounds like a bad idea, or is it quite all >> right because the overhead imposed by creating and deleting queues all >> the time is negligible? > > > ... this probably depends on the expected/required rate of requests. > > For low rates (say 100s or perhaps 1000s per second) it probably wouldn't > have too much impact, but as you start getting above that then you would be > spending time on queue creation and deletion that would be better spent > processing messages and requests. > > > > --------------------------------------------------------------------- > 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]
