Posts tagged 'amqp'
March 1, 2011
by
Jakub StastnyI decided to run some benchmarks of my AMQP encoder/decoder (AMQ Protocol gem) against the old one in the AMQP gem to see whether it performs better or not. So far I did only the most basic optimisations like storing reusable values in constants, nothing special (yet).
I did two sets of benchmarks: CPU time benchmarking using my fork of RBench with support for custom formatters (like writing results into a YAML file) and memory benchmarking using Object.count_objects
(Ruby 1.9).
January 19, 2011
by
Jakub StastnyI’m happy to announce that the AMQP 0.7 is released, as I promised in the previous blog post. So what are the changes?
January 12, 2011
by
Jakub StastnyIn the past year development of the AMQP gem was practicaly stagnating, as its original author Aman Gupta (@tmm1) was busy. A lot of bugs stayed unresolved, the code was getting old and out-dated and no new features or documentation were made.
At this point I started to talk with the RabbitMQ guys about possible collaboration on this. Actually originally I contacted VMware when I saw Ezra Zygmuntowicz looking for people to his cloud team, but when I found that VMware recently acquired the RabbitMQ project in London, I got interested. I signed the contract, switched from script/console
to Wireshark and the RabbitMQ Tracer and since November I’ve been happily hacking on the AMQP and AMQ-Protocol gems.
December 1, 2010
by
Michael BridgenWe have been prototyping support for a new protocol, as is our wont. This one is called “AMQP 1.0 R0”, and it is the new issue from the AMQP working group (of which RabbitMQ, and latterly VMware, are a member). The “R0” indicates that it’s the first revision of a recommendation. The specification is incomplete: there are many TODOs, and to a large extent it is unproven. Those two facts are part of what prompted this prototyping.
August 3, 2010
by
Michael BridgenSupport for AMQP’s basic.reject
just landed on default. It’s taken this long because we couldn’t agree on a single set of semantics that followed the specification, was actually useful, and wasn’t too complicated to implement.