Yes. This is something I think would be an interesting research
project, along with a generalisation of weak refs. It's fairly simple
to frame as a reinforcement learning problem. This is some work on
this, but I think tech. has moved on in important ways since.
N.
On Sun, Oct 17, 2010 at 12:04 P
Thanks for the info and ideas.
Since my app is Web server-like, I suspect that the thing to do in the
app for now to try to avoid GC delays when the app is non-idle (i.e., is
servicing one or more requests) is to trigger a GC at the point that an
app has been idle for N seconds.
N might be 1
Er, and maybe add to that scheduled GC strategy a sense of how
worthwhile we think a GC might be at that time, so that we're not just
doing, e.g., a GC 1 second after each request in a lightly-loaded
system, potentially delay service to the next request when GC wasn't needed.
Neil Van Dyke wro
On Sat, Oct 16, 2010 at 9:32 PM, Greg Hendershott
wrote:
> I thought I saw a thread devoted to calling collect-garbage
> periodically, when I browsed the web-server code before ... but I
> can't seem to find it again now.
The command line version used to do that... I think. I routinely
create suc
I thought I saw a thread devoted to calling collect-garbage
periodically, when I browsed the web-server code before ... but I
can't seem to find it again now.
> Eventually, we should improve the collector (or replace it with a
> better one) to support incremental collection.
My recent (albeit lim
On Sat, Oct 16, 2010 at 07:24:42PM -0600, Matthew Flatt wrote:
> At Sat, 16 Oct 2010 13:40:43 -0400, Neil Van Dyke wrote:
> > Any thoughts on how, by default, timing of garbage collection cycles is
> > affected by whether the process is "idle".
> >
> > For example, if non-GC threads are all waiti
At Sat, 16 Oct 2010 13:40:43 -0400, Neil Van Dyke wrote:
> Any thoughts on how, by default, timing of garbage collection cycles is
> affected by whether the process is "idle".
>
> For example, if non-GC threads are all waiting on events, might the
> thread with GC be more likely to trigger a GC
Any thoughts on how, by default, timing of garbage collection cycles is
affected by whether the process is "idle".
For example, if non-GC threads are all waiting on events, might the
thread with GC be more likely to trigger a GC at that idle time, rather
than when some threads are working?
R
8 matches
Mail list logo
