Feature request for FOG 1.6.x - Change database format from ISAM to INNODB

[george1421]

To allow FOG to process more transactions and to prevent heavy backlogs the FOG database structure should be changed from the ISAM engine to the INNODB engine. The issue is when many fog clients are in one FOG Server ream. The ISAM data engine does table locking on a record update. The INNODB engine uses row locking on an update. With table locking in isam, only one fog client can update a table at a time causing a back log on the SQL server and generating a heavy backlog of client transaction. This backlog causes a high CPU usage condition. This backlog doesn’t become an issue unless you have several hundred computers with the FOG client hitting the same master FOG server.

ref: https://forums.fogproject.org/topic/14254/high-cpu-usage

[Tom Elliott]

Fog 1.6 already does this

[george1421]

@Tom-Elliott said in Feature request for FOG 1.6.x - Change database format from ISAM to INNODB:

Fog 1.6 already does this

Nice!

So the zero in date issue has been resolved too? They kind of go hand in hand.

[Tom Elliott]

Let me clarify, it turns off the limitation preventing the update to move all tables to innodb.