mark yoffe wrote:
Hi
I am currently involwed in a project using rhmd
as far as i understand from threads posted here
rhmd is the trunk version of qpid with an extended plugin - used for
persistency which is based on Berkley DB
and does not support apache license that is why it is not part of the
standard destribution
(please corect me if i am wrong)
mostly, it does have high speed AIO store, mgnt, console, etc, extras.
for detailed
info on rhmd it would be better to ask on the
[EMAIL PROTECTED] list.
I will answer any qpidd questions here.
several questions
1 - Is there any reason to use the rhmd version does it offer any "extra"
features/benefits that are not part of qpidd?
see above.
2 - Is it problematic to use the trunk version in its current form ?
No issues using trunk, however note that trunk is under active development.
3 - what is the "future" plan for the trunk version (c++ broker specificlly)
, when is the Beta, or RC's planned as i currently see most efforts are
directed towords M2.1(maybe M2.2
as M2.1 just released officially )?
M2.1 was our last M2.x release, unless we find something that really
needs to be fixed on M2.x versions. M2.x
is a AMQP 0-8/9 version.
We currently are working to a M3 for trunk. For details on M3 see
http://cwiki.apache.org/qpid/roadmap.html, which
will be AMQP 0-10 (most of it) and backwards compat to M2.x for some of
the components. That matrix is on the
wiki. It might be M4 before everything is updated.
4 - If i am looking for the promissed Qpidd performence capabilities ( i
found reports on 300K messages per second ), what version should i use? does
the version affect performence?
and if so how high/low does the trunk score in that field ?
Performance is dependent on what client you use, hardware, OS tuning,
message size etc. C++ client
being the fastest. With a well tuned setup you can get why higher perf
than 300k msg/sec for message sizes
from 64 bytes to 1k. Larger messages sizes than that, you need 10G to
get high rates as you will become
bandwidth limited. Re-based versions of trunk is where the most of
performance testing has been done
for the C++ broker.
yes src rev does affect performance as the trunk perf may go up and down
based on check-ins, so there
are revisions that are faster than others, but just about any trunk
version can perform in the 300k/sec range with
basic tuning using C++ client on a multi core box. I have seem
throughput runs a lot higher than that. I can't
however publically disclose my employers benchmark data before they do,
but I can help you tune your setup if
you are willing to provide some details on it.
kind regards,
Carl.
