Allow eximstats to use InnoDB as the Database Engine
Completed
Currently eximstats maintenance (ex upcp) reverts the database engine to MyISAM. Eximstats, in its worst scenarios, can be very write-heavy and InnoDB alleviates this issue while from testing it appears to have a very positive effect on read times as well for WHM email reports returned almost instantly under InnoDB. As well, InnoDB appears to require fewer idle threads to process eximstats effectively.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Since there's been no feedback, we're going to consider this resolved at this point. The move to SQLite is now in a public build of version 64, 64.0.1, which is in the CURRENT tier. Update to version 64 now to take a look!
https://documentation.cpanel.net/display/64Docs/64+Release+Notes#id-64ReleaseNotes-eximstatsnowusesSQLite
Since there's been no feedback, we're going to consider this resolved at this point. The move to SQLite is now in a public build of version 64, 64.0.1, which is in the CURRENT tier. Update to version 64 now to take a look!
https://documentation.cpanel.net/display/64Docs/64+Release+Notes#id-64ReleaseNotes-eximstatsnowusesSQLite
This is something I'd like to hear further feedback from hosts on, but use of MyISAM has historically been intentional on our part given the general instability of InnoDB tables on shared hosting server environments.
Performance gains from InnoDB tend to take a back seat for cPanel items like the eximstats DB when InnoDB otherwise is intolerable of hard restarts, which is an unfortunate reality for many servers that cPanel & WHM operates within.
On servers that are well curated by a Linux sysadmin with experience managing InnoDB tables, this is likely an non-issue. If demand is there, I could see allowing a manual flag that allows use of InnoDB for such tables. Therefore, I encourage further discussion on this.
This is something I'd like to hear further feedback from hosts on, but use of MyISAM has historically been intentional on our part given the general instability of InnoDB tables on shared hosting server environments.
Performance gains from InnoDB tend to take a back seat for cPanel items like the eximstats DB when InnoDB otherwise is intolerable of hard restarts, which is an unfortunate reality for many servers that cPanel & WHM operates within.
On servers that are well curated by a Linux sysadmin with experience managing InnoDB tables, this is likely an non-issue. If demand is there, I could see allowing a manual flag that allows use of InnoDB for such tables. Therefore, I encourage further discussion on this.
I used to be gunshy on InnoDB as well, but with the advances in 5.5 and 5.6, I'm starting to see it handle adverse situations as well as MyISAM with its performance actually assisting in actively preventing adverse situations from arising. Along with the binlog and sensible backups, InnoDB for data integrity is relatively safe these days.
I used to be gunshy on InnoDB as well, but with the advances in 5.5 and 5.6, I'm starting to see it handle adverse situations as well as MyISAM with its performance actually assisting in actively preventing adverse situations from arising. Along with the binlog and sensible backups, InnoDB for data integrity is relatively safe these days.
In version 64 we've moved Eximstats to SQLite, which has resolved a lot of the reasons for wanting to move to InnoDB in this request. Would you consider taking a look at version 64 (currently only available in the EDGE tier) and letting me know if you think it resolves this request?
In version 64 we've moved Eximstats to SQLite, which has resolved a lot of the reasons for wanting to move to InnoDB in this request. Would you consider taking a look at version 64 (currently only available in the EDGE tier) and letting me know if you think it resolves this request?
Since there's been no feedback, we're going to consider this resolved at this point. The move to SQLite is now in a public build of version 64, 64.0.1, which is in the CURRENT tier. Update to version 64 now to take a look!
https://documentation.cpanel.net/display/64Docs/64+Release+Notes#id-64ReleaseNotes-eximstatsnowusesSQLite
Since there's been no feedback, we're going to consider this resolved at this point. The move to SQLite is now in a public build of version 64, 64.0.1, which is in the CURRENT tier. Update to version 64 now to take a look!
https://documentation.cpanel.net/display/64Docs/64+Release+Notes#id-64ReleaseNotes-eximstatsnowusesSQLite
Replies have been locked on this page!