<tdalign="left">The Assortment Cluster stores most of the page indexes.
Flushing speed of the temporary RWI cache depends on the size of this file cache. Increasing the space of this
cache will speed up crawls with a depth > 3.</td>
</tr>#(/useRWICache)#
</tr>
<trclass="TableCellDark">
<tdalign="left">HTTP Response Header</td>
@ -158,7 +158,7 @@
<tdalign="left">This is the database that holds the hash/url - relation and properties regarding the url like load date and server date.
This cache is very important for a fast search process. Increasing the cache size will result in more search results and less IO during DHT transfer.</td>
</tr>
#(usePreNURLCache)#::
<trclass="TableCellDark">
<tdalign="left">'pre-noticed' URLs</td>
<tdalign="right">#[slreqPreNURL]#</td>
@ -176,7 +176,7 @@
<tdalign="right">#[dfltPreNURL]#</td>
<tdalign="right">#[bestPreNURL]#</td>
<tdalign="left"></td>
</tr>#(/usePreNURLCache)#
</tr>
<trclass="TableCellDark">
<tdalign="left">'noticed' URLs</td>
@ -196,8 +196,8 @@
<tdalign="right">#[bestNURL]#</td>
<tdalign="left">A noticed URL is one that was discovered during crawling but was not loaded yet.
Increasing the cache size will result in faster double-check during URL recognition when doing crawls.</td>
</tr>
#(useEURLCache)#::
</tr>
<trclass="TableCellDark">
<tdalign="left">'error' URLs</td>
<tdalign="right">#[slreqEURL]#</td>
@ -216,7 +216,7 @@
<tdalign="right">#[bestEURL]#</td>
<tdalign="left">URLs that cannot be loaded are stored in this database. It is also used for double-checked during crawling.
Increasing the cache size will most probably speed up crawling slightly, but not significantly.</td>