Resizing should only have log N cost. It shouldn't be obvious with what you are seeing. The old copies should disappear pretty quickly next time there is a gc after resizing. Only the last resize or three will be around long enough to make it into tenured space and even then, this should collect pretty quickly.
THis isn't a first order effect. Something else is causing your grief. On Tue, Jul 21, 2009 at 7:41 PM, Grant Ingersoll <[email protected]>wrote: > I also notice we start with default values for the maps used to load the > models, which probably means we are resizing a lot. Should we use Strings > or would it be better to have some custom Writables and then keep track of > the actual terms separately kind of like the doc clustering does as well as > tracking the size so we can avoid resizing? > -- Ted Dunning, CTO DeepDyve
