sixcooler 916d79111e Runtime.maxMemory() DOES change @ runtime: ... I wondered getting Total-ram > Max-ram and MemoryControl.available() < 0 MemoryControl.available() < 0 causes some errors where its value is used for dimension of buffers for eg. git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@7852 6c8d7289-2bf4-0310-a012-ef5d649a1542		2011-07-19 12:48:50 +00:00
..
blob	changed handling of RowSet element retrieval: until today all elements had been copied from the underlying byte[] arrays into a new Entry object that again had a copy of a portion of that byte[] in its own bye[]. There was an option to just refer to the underlying byte[] with a pointer but that was almost never used. This commit now changes an interface to the Row class where it is now necessary to tell if a copy is always required. Fortunately the copy is only needed in very rare cases. That means that this change should cause much less memory allocation; it is expected that this happens especially during search situations.	2011-07-15 08:38:10 +00:00
data	changed handling of RowSet element retrieval: until today all elements had been copied from the underlying byte[] arrays into a new Entry object that again had a copy of a portion of that byte[] in its own bye[]. There was an option to just refer to the underlying byte[] with a pointer but that was almost never used. This commit now changes an interface to the Row class where it is now necessary to tell if a copy is always required. Fortunately the copy is only needed in very rare cases. That means that this change should cause much less memory allocation; it is expected that this happens especially during search situations.	2011-07-15 08:38:10 +00:00
index	changed the way how the index cache is flushed: do not flush when a put was made because that could cause that many put calls synchronize for a long time when the dump or a merge is performed. Instead a watchdog thread is doing the dump and therefore puts cannot block any more which is good when a put happens during a search result preparation.	2011-07-17 00:02:42 +00:00
io	the location search shows now not re-evaluated locations but only such locations that are attached as metadata to web pages	2011-03-30 23:26:36 +00:00
logging	- added a search option to filter only specific network protocols. i.e. get only results from ftp servers. Just add '/ftp' to your search.	2011-06-23 11:57:17 +00:00
order	- refactoring	2011-07-16 19:13:30 +00:00
rwi	more protection for the cleanup thread	2011-07-17 08:39:39 +00:00
table	changed handling of RowSet element retrieval: until today all elements had been copied from the underlying byte[] arrays into a new Entry object that again had a copy of a portion of that byte[] in its own bye[]. There was an option to just refer to the underlying byte[] with a pointer but that was almost never used. This commit now changes an interface to the Row class where it is now necessary to tell if a copy is always required. Fortunately the copy is only needed in very rare cases. That means that this change should cause much less memory allocation; it is expected that this happens especially during search situations.	2011-07-15 08:38:10 +00:00
util	Runtime.maxMemory() DOES change @ runtime:	2011-07-19 12:48:50 +00:00
workflow	- added a search option to filter only specific network protocols. i.e. get only results from ftp servers. Just add '/ftp' to your search.	2011-06-23 11:57:17 +00:00