High DB utilization
-
Everything had been running fine on our Fog server then last week the techs started complaining about slow performance and it was unusable. I connected to the server and mysql was bogging things down. I have tried upgrading to the latest with git. Same problem with the server. If I turn off the NIC port on the switch the utilization drops off to near normal. What should I look at?
-
@ljh How many computers with fog client installed are on this campus?
-
@george1421
When I go the hosts section under FOG and click list all hosts it never loads anything. The database is old but I think there are maybe 4500 computers active in there. -
@ljh What I’m asking is that actively how many computers with FOG Client is installed, is currently hitting this fog server. Is 4,000 the right number? If yes then when you look at the
topcommand and sort byProcessor do you see mysql at the top and many php-fpm processes under it?If you set the fog client check in from 5 minutes (300 seconds) to 15 minutes (900) seconds does that fix some of the performance issues with the FOG web ui?
If yes then we may need to make an adjustment to the FOG server db.
-
@george1421 When I run top and hit P mysql is the top process. I did backup the fog DB and then I dropped it. I did the install again and then imported the DB back in. The utilization dropped to almost nothing. Right now everyone is off for the 4th of July week. On Monday I will see if this the fix. We have around 4000 clients but this is summer time and of those 4000 only about 400 are active on the network during summer.
-
@ljh OK if this still a problem we might want to check to see if the fog database tables are in myisam or innodb format. Switching them over to innodb should fix the responsiveness of the database: https://forums.fogproject.org/topic/16099/configure-fog-database-to-use-innodb-engine
-
@ljh Everything worked fine yesterday. The techs even told me that it hasn’t run that fast in a while. So it looks like that fixed my issue.
-
@ljh said in High DB utilization:
So it looks like that fixed my issue
FWIW: Which “that” is the fix? Switching over to innodb engine or the reboot?