> -----Original Message-----
> From: Peter Royal [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 28, 2001 11:09 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [c2] EventCache questions
> 
> 
> At 10:48 AM 8/28/2001 -0400, you wrote:
> >Wow, where have you been before? :)))
> >Yes, you are right - that's not necessary and this might be the 
> >performance issue.
> >Reducing checker threads amount down to one would decrease amount of 
> >runFinalization()/gc()
> >calls in two times - giving better performance.
> >
> >Could we use just one static checker thread?
> >There is an issue with configuration though... Which configuration to use, 
> >from what store...
> 
> How about a separate component to do the checking? (MRUMemoryStoreJanitor?) 
> Each MRUMemoryStore would register its requested heapsize & freememory with 
> the janitor, and it would be responsible for the worker thread. It would 

Good suggestion and I kind of like this name ;)
Gerhard, what do you think?


> try to keep the JVM totalMemory below the sum of all the registered 
> heapsizes, and freeMemory below the sum of all registered freememories.

Here I think that idea (originally) was that heapsize specifies heapsize of the JVM,
but not the size of the store (because it is (almost) impossible to determine), so my 
understanding is that these parameters (heapsize and freememory) should also 
go into janitor configuration.


> 
> If runFinalization/gc isn't enough to create the free memory, a round-robin 
> approach (or other algorithm) could be used to select a MRUMemoryStore to 
> free an object from.

Agree.


> 
> Some of the current MRUMemoryStore parameters would now be Janitor 
> parameters (namely cleanupthreadinterval and threadpriority).

heapsize and freememory also (see above)

> 
> Just my .02 :)

Thanks,
Vadim

> -pete
> 
> -- 
> peter royal -> [EMAIL PROTECTED]
> managing partners, inc. -> http://www.managingpartners.com
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to