[moe]

Given the same semantics, RabbitMQ pushes 100k+ per core as well.

Until it grinds to a halt for no obvious reason</snark>

We've dropped RabbitMQ on a project a while ago not for performance but for stability and opacity reasons.

I went into detail about the issues in a post a few months ago so I'll skip that here. My take-home is that unless you have complex routing requirements that can only be realized with AMQP then you should think long and hard if you really want the aircraft carrier of a component that is RabbitMQ in your dependency list.

Redis/Resque, beanstalk and Celery cover the overwhelming range of use-cases just fine and are complete no-brainers to operate in contrast to wrestling with AMQP topologies, flakey client libraries and an opaque (to most) erlang blackbox.