Dne ne 25. listopadu 2018 Michal Čihař napsal(a): > Hi > > Slávek Banko píše v So 24. 11. 2018 v 06:51 +0100: > > Rebuild indexes completed: > > > > $ du -Shs data/whoosh/ > > 1,5G data/whoosh/ > > > > But huge memory consumption remains: Main celery process 156 MiB, > > worker > > 1310 MiB and still growing... > > The memory consumption looks really high to me. For example on Hosted > Weblate service the Whoosh index is 11G and the workers consume > something like 100-200M. Are you on Python 2 or 3? What Whoosh version > are you using?
Ahoj Michale, a few days ago I updated Weblate on our server to version 3.3.0 and the behavior was "interesting". During a time when the celery started, everything was all right. The memory consumption was at a good level - main process of about 100 MiB, a worker of about 150 MiB. The suspect was only a constant CPU usage. I courageously increased the number of workers from 1 to 2. At begin everything looked good. But after a while, workers began to increase their memory consumption - sometimes significantly, however after some time gradually releasing them. Each worker then consumed about 350 - 450 MiB. Later, however, the main process, which typically consumed 100 MiB, began to significantly increase memory consumption - reaching 900 MiB. Each worker still showed a continuous CPU usage. I preventively stopped the celery and started again. To my surprise, since then behaviour of celery has been totally in order. The control process has a consumption of about 100 MiB, each worker of about 150 MiB. And the CPU consumption is low. I do not know what it was like before, but now for two days, the behavior is absolutely seamless. Thank you for your support! Cheers -- Slávek
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Weblate mailing list [email protected] https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
