On 07/11/2015 05:52 PM, Fraser Adams wrote:
On point b. has anyone (most likely Gordon) explored the scaling limits
of qpidd? Obviously when Qpid started out servers tended to have
something between one and four cores, but now of course Moore's law
tends to be followed by increasing the number
On 11 July 2015 at 17:52, Fraser Adams fraser.ad...@blueyonder.co.uk wrote:
Hey all,
Suppose I have a queue on qpidd, I know that I can have multiple consumer
clients subscribing to that queue node - I've used that several times to
provide a means of scaling out consumers, so if I have n
On Sun, 2015-07-12 at 09:14 +0100, Fraser Adams wrote:
As I say I think that ActiveMQ Apollo started out because of scaling
limitations of the original ActiveMQ and has evolved to a reactor
based
threading model built on hawt-dispatch (Java implementation of Grand
Central Dispatch
Hi Steve,
Thanks for the response.
Sorry yeah I remembered after I posted that there was a thread pool that
was number of cores + 1, What I was meaning (in my own mind at least, if
not what I wrote :-D ) was that the threading was *related* to
connection (as opposed to per connection D'oh!!)
Hey all,
Suppose I have a queue on qpidd, I know that I can have multiple
consumer clients subscribing to that queue node - I've used that several
times to provide a means of scaling out consumers, so if I have n
consumers each consumer receives roughly 1/n of the messages published
onto the
Hi Frase,
You’ve done a good job at guessing the limits - I’ll let Gordon educate us on
the rest.
The threading model, though - definitely not per connection. There’s a pool of
threads that can handle I/O - by default there are (number of cores) + 1, but
you can change it by command line
