7 Commits

Author	SHA1	Message	Date
Michael Peter Christen	d3964253ae	- added @SuppressWarnings to unused servlet method parameters ... - removed unnecessary casts - removed unnecessary throw statements	2012-07-05 09:14:04 +02:00
sixcooler	985b78cf89	correct 'avaiable()' to use max of young / eden	2012-01-16 16:59:58 +01:00
sixcooler	c9aaa9e00a	respect non-reserved Memory in GenerationMemoryStrategy ... and enable it again	2012-01-16 01:46:12 +01:00
sixcooler	448656087a	probably fix for http://bugs.yacy.net/view.php?id=94 ... (don't know how to force this exception)	2011-12-06 02:49:58 +01:00
sixcooler	d40a177c05	Generation Memory Strategy fine tuning ... add some log-output in termlist_p git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@7904 6c8d7289-2bf4-0310-a012-ef5d649a1542	2011-08-27 15:23:24 +00:00
sixcooler	839f407fe4	Generation Memory Strategy fine tuning: ... - some more optimism on requests of unknown values - avoid a premature value of 0 byte available git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@7903 6c8d7289-2bf4-0310-a012-ef5d649a1542	2011-08-25 22:32:15 +00:00
sixcooler	4fec99115b	Implementation of strategies for controlling memory resources. ... You can toggle between previous (standard) and new (generation) strategy at PerformanceMemory_p.html. The generation memory strategy is implemented with the objective of running more robust but with the cost of early stopping some tasks (eg. dht) while running low on memory. This new strategy does respect the generational way a heap is organized on most used jvms. These changes run fine on my 3 peers for weeks now, but as I'm human, I may fail. Please be carefull using generation memory strategy and report errors by naming OS, jvm and java_args. git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@7886 6c8d7289-2bf4-0310-a012-ef5d649a1542	2011-08-22 17:50:03 +00:00