You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Michael Peter Christen ca8b100f96 run the cleanup process even when load is high, do postprocessing even ... if load > 1 (but < 2) but only if there is enough memory (now: 0.5 GB RAM available). The memory amount of the postprocessing is the cause that systems block because they run into a frequent-GC chain which almost locks the peer. If running with enough memory, the postprocessing is fast and not damaging to the system. Because the required RAM of 0.5 GB is never available in default setting, the postprocessing will not run if the peer is not reconfigured to use more memory.		11 years ago
..
index	catch solr close exceptions	11 years ago
query	extra sleep for remote searches enhances search results because there is	11 years ago
ranking	- the webgraph shall store all links which appear on a web page and not	12 years ago
schema	added memory protection for postprocessing	11 years ago
snippet	enhanced webgraph processing	11 years ago
EventTracker.java	- replaced all length() == 0 and size() == 0 with isEmpty()	13 years ago
IndexAbstracts.java	refactoring:	14 years ago
IndexingQueueEntry.java	refactoring	13 years ago
MemoryTracker.java	- refactoring of log to ConcurrentLog:	12 years ago
ResourceObserver.java	found and fixed a huge memory leak in solr caching (inside Solr). The	11 years ago
Shutdown.java	Added 'final' for all exception blocks as this helps the Java compiler	12 years ago
StorageQueueEntry.java	added missing class	12 years ago
Switchboard.java	run the cleanup process even when load is high, do postprocessing even	11 years ago
SwitchboardConstants.java	removed jena library and all code that depended on jena. When jena was	11 years ago