From d23d2496522923d25e1ffb04d82a0b986387f236 Mon Sep 17 00:00:00 2001 From: Patrick Uiterwijk Date: Sun, 1 Nov 2015 01:04:35 +0000 Subject: [PATCH] Decrease the number of mm_crawler threads It seems like an update caused the crawler to use slightly more memory than before, meaning the previous tuning of 27 threads no longer fits in the server's memory. This patch brings it down to 23, which is for now known-good. We should look again at what values to use after freeze. Signed-off-by: Patrick Uiterwijk --- roles/mirrormanager/crawler/files/crawler.cron | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/mirrormanager/crawler/files/crawler.cron b/roles/mirrormanager/crawler/files/crawler.cron index 8ace23d6f7..a3691d7732 100644 --- a/roles/mirrormanager/crawler/files/crawler.cron +++ b/roles/mirrormanager/crawler/files/crawler.cron @@ -5,4 +5,4 @@ # [ "`hostname -s`" == "mm-crawler02" ] && sleep 2h is used to start the crawl # later on the second crawler to reduce the number of parallel accesses to # the database -0 */12 * * * mirrormanager [ "`hostname -s`" == "mm-crawler02" ] && sleep 2h; /usr/bin/mm2_crawler --timeout-minutes 180 --threads 27 `/usr/local/bin/run_crawler.sh 2` > /dev/null 2>&1 +0 */12 * * * mirrormanager [ "`hostname -s`" == "mm-crawler02" ] && sleep 2h; /usr/bin/mm2_crawler --timeout-minutes 180 --threads 23 `/usr/local/bin/run_crawler.sh 2` > /dev/null 2>&1