Relatively High CPU Usage by Gunicorn on Idle Discovery

[stan.v...@exlhub.com]

Running "top", I noticed that my idle install of Ginkgo Discovery consumes 3-5% of the CPU by each of the two gunicorn worker, and if I increase the # of workers to 5 - now I have 5 workers at 3-5% CPU each, constantly; no python processes. In contrast with this, an idle LMS install seems to be consuming almost zero CPU, and it shows a number of python and guncorn processes. Digging a little deeper, I see that LMS gunicorn workers appear to be "sync" vs. Discovery's are "async". If I change Discovery workers to "sync" (just for testing of this described behavior) - they still consume the same amount of CPU. I don't see any activity in the logs, and if I execute Discovery via runserver - likewise, it shows no activity but still 7-8% of the CPU usage it "top" (by the python process in this case). Looking at the Installed Apps I can't pin point which one would be acting in the background and consuming the CPU, so I'm really puzzled, and would like to find an explanation and a potential way to tune Discovery to lower the idle CPU usage. Any suggestions?

[stan.v...@exlhub.com]

Finally got a chance to take a closer look. The issue was with "--reload" in /edx/app/discovery/discovery.sh, which came from the Configuration repo, docker\build\discovery\ansible_overrides.yml. Once removed, the idle CPU is where it should be - near zero