Version française
Home     About     Download     Resources     Contact us    
Browse thread
Weak hashtables & aggressive caching
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Matt Gushee <matt@g...>
Subject: Re: [Caml-list] Weak hashtables & aggressive caching
Jacques Garrigue wrote:

> I wonder how you trigger the GC, to both keep the cache long enough,
> and to avoid filling the memory too much, and resulting in lots of
> swapping.

I wasn't planning to trigger the GC explicitly. My thought was simply to 
stop preloading before GC begins (or at least *when* GC begins).

> means that the memory set should not increase. But with external data
> structures like pixbufs, the GC is called in a pre-programmed way,
> currently at least after every 10 pixbuf allocations.

You mean that LablGTK directly invokes the garbage collector after 10 
images. That's not much (unless, of course, they are big images). Sounds 
like it's a lot of trouble for a small benefit.

-- 
Matt Gushee
: Bantam - lightweight file manager : matt.gushee.net/software/bantam/ :
: RASCL's A Simple Configuration Language :     matt.gushee.net/rascl/ :