On Mar 26, 2012, at 2:50 AM, Tomas Vondra wrote:
> Hi all,
>
> today I've noticed this link on HN: http://plasma.cs.umass.edu/emery/hoard
>
> Seems like an interesting option for systems with a lot of CPUs that are
> doing a lot of alloc operations. Right now I don't have a suitable system
> to
2012/3/26 Tomas Vondra :
> Hi all,
>
> today I've noticed this link on HN: http://plasma.cs.umass.edu/emery/hoard
>
> Seems like an interesting option for systems with a lot of CPUs that are
> doing a lot of alloc operations. Right now I don't have a suitable system
> to test it - anyone tried to b
Hi all,
today I've noticed this link on HN: http://plasma.cs.umass.edu/emery/hoard
Seems like an interesting option for systems with a lot of CPUs that are
doing a lot of alloc operations. Right now I don't have a suitable system
to test it - anyone tried to benchmark it?
Tomas
--
Sent via p
Baron Swartz's recent post [1] on working set size got me to thinking.
I'm well aware of how I can tell when my database's working set
exceeds available memory (cache hit rate plummets, performance
collapses), but it's less clear how I could predict when this might
occur.
Baron's proposed method f
