9,280
edits
Advanced sync setup: Difference between revisions
Jump to navigation
Jump to search
→Sync log information
| Line 167: | Line 167: | ||
This text is permanently stored in the log before the first use of the advanced settings. (For the case something goes wrong.) Sync log contains additional information that is important for designing downloader cache. It might look similar to <code><Downloader CacheSize=200MB UsedCache=50MB /></code>. In this case, we designed an unnecessary large cache. This does not present any problem because the cache grows dynamically (DownloadCacheSize is just theoretical upper limit), yet it is good to know the real memory consumption. | This text is permanently stored in the log before the first use of the advanced settings. (For the case something goes wrong.) Sync log contains additional information that is important for designing downloader cache. It might look similar to <code><Downloader CacheSize=200MB UsedCache=50MB /></code>. In this case, we designed an unnecessary large cache. This does not present any problem because the cache grows dynamically (DownloadCacheSize is just theoretical upper limit), yet it is good to know the real memory consumption. | ||
The downloader summary may contain also the information about the pauses ,as for example <code><Downloader CacheSize=100MB UsedCache=81MB Paused=18% /></code>. In this case, we know that the downloader paused for a considerable time. As the single possible reason is insufficient cache size, increasing the cache size would improve the performance. | The downloader summary may contain also the information about the pauses, as for example <code><Downloader CacheSize=100MB UsedCache=81MB Paused=18% /></code>. In this case, we know that the downloader paused for a considerable time. As the single possible reason is insufficient cache size, increasing the cache size would improve the performance. Also check your data for [[Advanced_sync_setup#Dominant_entity|dominant entities]]. | ||
== Warning == | == Warning == | ||