Hi Thomas, > > That's bad. I guess that's not acceptable. Is it only when using the > SoftReference, or also when using WeakReference? Soft anyway doesn't > make sense (in my view).
It is only with soft cache and only under corner cases. In my test case I tryed to load huge file into memory. I dont think it is problem, it is more like 'feature'. Weak references does not have this problem, they are GCed very fast. > > Why do you think so? I don't plan to add a dependency to the Google > collection. > MapMaker have reference disposal in separate thread, so memory can be reclaimed faster. Problem is that this depends on concurrent-util from 1.5. So it is not propably an option. I still think my patch is good and I am not making any changes. But maybe I would update documentation and recommend WEAK with -server JRE command line option (will improve GC). Regards, Jan Kotek --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
