[rabbitmq-discuss] New Persister merged into default

[Aaron Westendorf]

Bummer, that's a big surprise.  I'd be curious to see a comparison
with a persister backed by a storage engine that does use mmap, like
Tokyo Cabinet.  Not that I doubt the team's abilities, we just have
had fantastic results with applications such as Varnish, TC and Mongo
which all make extensive use of mmap and let the kernel do all the
heavy lifting.  Maybe with the abstraction layer in place, we'll take
that on the next time we have a hack-a-thon day.  I'd also be curious
to try an extension of the persistent messaging, so that after X
seconds it can be thrown out.

We've decided to hold off upgrading our cluster until the next release
of Rabbit which includes this persister, we're looking forward to it.
Well done!

cheers,
Aaron

On Wed, Aug 11, 2010 at 8:17 AM, Matthew Sackman <matthew at rabbitmq.com> wrote:
>
> Sadly, no: Erlang does not expose an mmap interface, though actually
> there has been a recent thread on erlang-questions about how to
> implement this. However, we do do very aggressive caching and work hard
> to make as much use of kernel disk buffers as possible: we try to play
> nice with the kernel. With a little tuning, we can easily saturate disk
> write bandwidth, so it seems we're doing something right ;)
>
> Matthew
>



-- 
Aaron Westendorf
Senior Software Engineer
Agora Games
359 Broadway
Troy, NY 12180
Phone: 518.268.1000
aaron at agoragames.com
www.agoragames.com