YaCy '#[clientname]#': Performance Settings for Memory

#[metas]# #[header]#

Performance Settings for Memory

RAM Cache for Database Files:

Database

Chunk Size
(bytes)

#Needed Slots
(= DB Size)

#Empty Slots

#Used Slots
High Priority

#Used Slots
Medium Priority

#Used Slots
Low Priority

Used
Size

Assigned
Max-Size

Recommended
Max-Size

Optimum
Max-Size

Description

RWI Assortment Cluster

#[chunkRWI]#

#[slreqRWI]#

#[slempRWI]#

#[slhigRWI]#

#[slmedRWI]#

#[sllowRWI]#

#[usedRWI]#

bytes

#[goodRWI]#

#[bestRWI]#

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.

HTTP Response Header

#[chunkHTTP]#

#[slreqHTTP]#

#[slempHTTP]#

#[slhigHTTP]#

#[slmedHTTP]#

#[sllowHTTP]#

#[usedHTTP]#

bytes

#[goodHTTP]#

#[bestHTTP]#

The Response Header database stores the HTTP heades that other servers send when YaCy retrieves web pages during proxy mode, when performing crawls or if it fetches pages for snippet generation. Increasing this cache will be most important for a fast proxy mode.

'loaded' URLs

#[chunkLURL]#

#[slreqLURL]#

#[slempLURL]#

#[slhigLURL]#

#[slmedLURL]#

#[sllowLURL]#

#[usedLURL]#

bytes

#[goodLURL]#

#[bestLURL]#

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.

'noticed' URLs

#[chunkNURL]#

#[slreqNURL]#

#[slempNURL]#

#[slhigNURL]#

#[slmedNURL]#

#[sllowNURL]#

#[usedNURL]#

bytes

#[goodNURL]#

#[bestNURL]#

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.

'error' URLs

#[chunkEURL]#

#[slreqEURL]#

#[slempEURL]#

#[slhigEURL]#

#[slmedEURL]#

#[sllowEURL]#

#[usedEURL]#

bytes

#[goodEURL]#

#[bestEURL]#

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.

DHT Control

#[chunkDHT]#

#[slreqDHT]#

#[slempDHT]#

#[slhigDHT]#

#[slmedDHT]#

#[sllowDHT]#

#[usedDHT]#

bytes

#[goodDHT]#

#[bestDHT]#

This is simply the cache for the seed-dbs (active, passive, potential). This cache is divided into three equal parts. Increasing this cache may speed up many functions, but we need to test this to see the effects.

Messages

#[chunkMessage]#

#[slreqMessage]#

#[slempMessage]#

#[slhigMessage]#

#[slmedMessage]#

#[sllowMessage]#

#[usedMessage]#

bytes

#[goodMessage]#

#[bestMessage]#

The Message cache for peer-to-peer messages. Less important.

Wiki

#[chunkWiki]#

#[slreqWiki]#

#[slempWiki]#

#[slhigWiki]#

#[slmedWiki]#

#[sllowWiki]#

#[usedWiki]#

bytes

#[goodWiki]#

#[bestWiki]#

The YaCy-Wiki uses a database to store its pages. This cache is divided in two parts, one for the wiki database and one for its backup. Increasing this cache may speed up access to the wiki pages.

News

#[chunkNews]#

#[slreqNews]#

#[slempNews]#

#[slhigNews]#

#[slmedNews]#

#[sllowNews]#

#[usedNews]#

bytes

#[goodNews]#

#[bestNews]#

The News-DB stores property-lists for news that are included in seeds. Increasing this cache may speed up the peer-ping.

Changes take effect after re-start of YaCy

#[footer]#