If you are using the concurrent collector on an active system, you should be getting parallel collections pretty often. Each of these will increment the generation for the objects.
Thus, long-lived means t > tenuring-age x new-space-collection-interval. My guess is that this typically reduces to t > a few minutes. The scary part, though, is whether refreshing the model will invoke a stop and collect operation on the entire heap. Load testing is very important here because you need to know that if you starve the parallel collector of CPU time that it will still succeed without long pauses. On Thu, Nov 12, 2009 at 12:55 PM, Sean Owen <[email protected]> wrote: > It should, yes. Almost all the memory is long-lived (well, relative > not-short-lived) even during the transition. > > On Thu, Nov 12, 2009 at 8:48 PM, Otis Gospodnetic > <[email protected]> wrote: > > Does this hold true even if you refresh the whole model fairly > frequently, say every 5, 10, 15, or 60 minutes? > -- Ted Dunning, CTO DeepDyve
