> Ken, > > QMFv2 solves this issue, can't we port the tools to QMFv2? >
We're already part way there - the tools use the pure python qmf implementation, which supports v2 map data. There may be issues with using the tools against older v1-only brokers - I'd have to think about that. But I'd really want to pinpoint the source of the perf issue first - my theory could be wrong. > Carl. > > > On 07/21/2011 01:47 PM, Ken Giusti wrote: > > Alan's correct - I *believe* (not looking at the code in the > > debugger ATM) that qpid-config is most likely downloading the broker > > schema data on connection, and perhaps parsing that - all under > > python. > > > > So I don't think bringing up the connection is the problem - it's > > more like pulling in all the QMF-related data once we're connected, > > but before we can issue commands. > > > > No doubt that whole approach could use a little performance > > tuning.... > > > > -K > > > > ----- Original Message ----- > >> On 07/20/2011 10:43 AM, Pavel Moravec wrote: > >>> Hi all, > >>> I realised on every qpid version& system I used a poor performance > >>> of qpid-config tool. It usually takes 2 to 3 seconds to execute a > >>> command, e.g.: > >>> > >>> # time qpid-config add queue test > >>> > >>> real 0m2.243s > >>> user 0m0.161s > >>> sys 0m0.027s > >>> # time qpid-config del queue test > >>> > >>> real 0m2.303s > >>> user 0m0.208s > >>> sys 0m0.037s > >>> # > >>> > >>> I wrote a simple C++ program to emulate some parts of qpid-config > >>> tool by connecting to the broker and sending proper QMF > >>> message(s). > >>> The program executes equivalent stuff almost instantly. > >>> > >>> Why is qpid-config so slow? Is there some timeout waiting for > >>> (potentially negative) response? Does it make sense / would not it > >>> be usefull to speed it up? > >>> > >> It's an issue with QMF. Setting up the initial QMF connection is > >> very > >> slow. I'm > >> not sure why. It most definitely would be good to speed it up, it > >> annoys me no end. > >> > >> If you have a large number of operations to do, you can write your > >> own > >> client in > >> python that sets up the QMF connection once, then uses it to do all > >> the work. > >> That's not particularly easy right now, qpid-config is not set up > >> to > >> be reused > >> like that. It would be nice to have a little python API that > >> mirrors > >> the command > >> line arguments to qpid-config. It would be even nicer to fix the > >> real > >> problem by > >> getting the QMF init time down to something reasonable. > >> > >> --------------------------------------------------------------------- > >> Apache Qpid - AMQP Messaging Implementation > >> Project: http://qpid.apache.org > >> Use/Interact: mailto:[email protected] > > --------------------------------------------------------------------- > > Apache Qpid - AMQP Messaging Implementation > > Project: http://qpid.apache.org > > Use/Interact: mailto:[email protected] > > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
