On 17/05/12 20:47, Simon Helsen wrote:
yes, doing a gc has its issues in general, especially on a server, but
we'd only do it at the very beginning (after startup) or offline. As I
mentioned before, it doesn't really work reliably. It only increases the
chance the lock is released.
But for that reason, we are stuck to direct. It also worth noting that
direct is faster on Windows, at least, it was last time we tested. On
linux, mapped seems somewhat faster
Simon
A thing to try is to use Google's guava cache code.
Even better, would be a scan resistant algorithm, like LRU-2 (LRU-K), 2Q
or ARC. This is a patented area ... it's IBM who patented ARC.
For the PostgreSQL story:
http://www.varlena.com/GeneralBits/96.php
(which means the postgresql algorithm is an interesting choice)
Andy
