Re: Thoughts on proton performance and interoperability testing
I've got a amqp benchmarking project started at: https://github.com/chirino/amqp-benchmark It measures sender/consumer throughput under a bunch of different usage scenarios. Let me know what your think. We could bring it into the qpid project if it would make it easier to collaborate on it here. On Thu, Jan 31, 2013 at 9:41 AM, Ken Giusti kgiu...@redhat.com wrote: Hi Folks, I'd like to solicit some ideas regarding $SUBJECT. I'm thinking we could take an approach similar to what is done on the C++ broker tests now. That is we should develop a set of native send and receive programs that can be used to profile various performance characteristics (msgs/sec with varying size, header content encode/decode etc). By native I mean implementations in Java and C. I've hacked our C send and recv examples to provide a rough swag a measuring msgs/sec performance. I use these to double check that any changes I make to the proton C codebase do not have an unexpected impact on performance. This really belongs somewhere in our source tree, but for now you can grab the source here: https://github.com/kgiusti/proton-tools.git We do something similar for the QPID broker - simple native clients (qpid-send, qpid-receive) that do the performance sensitive message generation/consumption. We've written python scripts that drive these clients for various test cases. If we follow that approach, not only could we create a canned set of basic benchmarks that we could distribute, but we could also build inter-opt tests by running one native client against the other. E.g. C sender vs Java receiver. That could be a useful addition to the current unit test framework - I don't believe we do any canned interopt testing yet. Thoughts? -K -- ** *Hiram Chirino* *Engineering | Red Hat, Inc.* *hchir...@redhat.com hchir...@redhat.com | fusesource.com | redhat.com* *skype: hiramchirino | twitter: @hiramchirinohttp://twitter.com/hiramchirino * *blog: Hiram Chirino's Bit Mojo http://hiramchirino.com/blog/*
Re: JNI branch merged to trunk
Looks good. I've just pulled a clean version of lastest trunk. I was able to build and run all tests (proton-j, -c, -jini) on my Fedora 17 box just fine. One note to proton-c oriented folks: read the top level README file. You need to mkdir the 'build' directory at the top level rather than from the proton-c dir [at least I had to - the old way no longer appears to work]. -K - Original Message - Keith and I have just merged the jni-binding branch to trunk. We've tested our changes using the Python test suite and by running the release.sh script. Nevertheless, this is quite a big commit so some perturbation of your work is possible. Let us know if you have any questions. For your convenience, here is the commit message: r1441401 | philharveyonline | 2013-02-01 11:54:38 + (Fri, 01 Feb 2013) | 12 lines PROTON-191, PROTON-192, PROTON-193, PROTON-194, PROTON-210: merged jni-binding branch to trunk, containing the following changes in descending order of impact: - PROTON-194: modified CMake and Maven build systems to operate from the top level. CMake now also builds Java. - PROTON-192: added JNI bindings for proton-c - PROTON-210: simplifications to release.sh because we now release a single tarball from the top level - PROTON-193: Add setPeerHostname/getPeerHostname to Proton Java API - PROTON-191: added API reconciliation tool in design/ folder to assist our harmonisation efforts. Merge command was: $ svn merge --reintegrate https://svn.apache.org/repos/asf/qpid/proton/branches/jni-binding Phil
Proton Perl bindings now in Fedora
The package review went very quickly, and the bindings are now up. Please install them, test them and then give us some karma. F17: https://admin.fedoraproject.org/updates/perl-qpid_proton-0.3-2.fc17 F18: https://admin.fedoraproject.org/updates/perl-qpid_proton-0.3-2.fc18 -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ pgp6Xv2Fgnz8t.pgp Description: PGP signature
