On Mon, Nov 22, 2010 at 6:42 PM, Sylvain Le Gall <sylvain@le-gall.net> wrote:
On 22-11-2010, Damien Doligez <damien.doligez@inria.fr> wrote:->
>
> On 2010-11-21, at 20:26, Eray Ozkural wrote:
>
>> I've been thinking whether some kind of doubling strategy would work for the minor heap size. What do you think?
>
> Sounds like an interesting idea, but what heuristic would you use?
> When everything is smooth, the running time decreases something like
> exponentially with the minor heap size, so you'd always want to
> increase the size. How do you tell when to stop? And then, if the
> program is not behaving uniformly, when do you decide to reduce
> the size?
>
How do you tell when to stop?
Maybe you can stop when you reach (the size of the L2/L3 cache of the
processor) / number of core.
Both information are quite straight to read from /proc/cpuinfo.