API_WORKERS default too high on machines with many CPUs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Triaged
|
Low
|
Unassigned |
Bug Description
I've installed devstack on some machines with as many as 256 CPUs. stackrc has:
API_
so a lot of the services end up getting configured with 64 workers. This causes massive numbers of connections to mysqld and ends up hammering mysqld with a large number of heartbeats (from nova services AFAICS).
(This in turn seems to cause mysqld to reach sustained writes to disk of 2--5 MB/s. In theory heartbeats shouldn't cause it to write to disk at all, and I'm not entirely sure yet but it looks like this is happening due to another bug where after every SQL SELECT heartbeat something is also triggering a COMMIT then a ROLLBACK. I'll file a separate bug for that though.)
I suggest capping API_WORKERS at 8 or 16 which should be enough for devstack scenarios.
Changed in devstack: | |
status: | New → Triaged |
importance: | Undecided → Low |
Notice that due to bug #1838689, lowering API_WORKERS does not currently lower neutron's number of RPC workers. However that will be fixed by https:/ /review. opendev. org/#/c/ 674125/