Revision history [back]

Hi, I have the same problem. The controller node is itself virtualized. But it doesn't matter it was running happily until keystone were to apache. Then it started to take a lot of processes and memory. The database itself (mysql) it's also taking huge amount of memory. I think ceilometer has something to do here.

I'm trying to optimize database but I don't know I think there must be other problems.

2003 mysql 20 0 2170292 345324 8324 S 2,0 8,6 167:09.61 mysqld
2603 nova 20 0 790156 168864 4512 S 1,3 4,2 548:30.13 nova-api
2584 nova 20 0 291228 117016 4000 S 4,3 2,9 890:06.63 nova-conductor
2583 nova 20 0 289636 115516 4000 S 3,7 2,9 814:37.26 nova-conductor
2585 nova 20 0 289636 114784 3952 S 2,0 2,8 888:48.33 nova-conductor
7069 keystone 20 0 502240 107500 8952 S 0,0 2,7 0:05.61 apache2
7071 keystone 20 0 502232 107464 8936 S 0,0 2,7 0:05.48 apache2
7070 keystone 20 0 436184 106892 8952 S 0,0 2,7 0:05.34 apache2
16597 neutron 20 0 331456 103188 4316 S 0,0 2,6 65:08.53 neutron-server
2383 nova 20 0 284772 103144 4220 S 2,0 2,6 371:14.04 nova-scheduler
16596 neutron 20 0 331200 102672 4312 S 0,0 2,5 65:15.84 neutron-server
16599 neutron 20 0 331456 99700 4340 S 0,0 2,5 24:59.80 neutron-server
2372 nova 20 0 281704 97784 4180 S 0,0 2,4 34:54.86 nova-consoleaut
2602 nova 20 0 790380 93028 4292 S 2,0 2,3 331:44.91 nova-api
15771 neutron 20 0 325568 89428 5568 S 0,7 2,2 16:04.99 neutron-server
1536 rabbitmq 20 0 1912260 89024 3300 S 1,0 2,2 419:33.64 beam.smp

I will check again but I thing there's too much activity for this small installation. Server is normally above 20% usage... I was expecting things get quiter.