Hi @<1523701868901961728:profile|ReassuredTiger98> , this simply might be an issue of too few handler processes un the ClearML apiserver (unless the pressure is on the databases). You can easily change that (the default is 8
) using the CLEARML_GUNICORN_WORKERS
environment variable passed to the apiserver service)
Hi @<1523701087100473344:profile|SuccessfulKoala55> I tested it and this seems not to be the issue. When looking at my server I can see that ElasticSearch utilizes a single core with 100%. This is the only observation that I made. May it be that elasticsearch is the issue?
Hi Jake, thank you very much for the suggestion. I will try that!