My guess is that it's simply due to the interpreted nature of python. I've been writing a Java port of qpid-config that uses QMF2 and that similarly takes a little time to give results, but that's pretty much down to the JVM startup. I wrote code to listen out for QMF Events and that responds to Events really quickly - and my Event handler is doing the same sort of thing as qpid-config - b queues, so I'd be willing to bet that it is just due to the time taken to fire up the python interpreter.
Regards, Fraser 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.: > > Kind regards, > Pavel > -- View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/qpid-config-slow-tp6602945p6603440.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
