Kush Rohra Posted March 26, 2018 Report Posted March 26, 2018 Hello, I would like to ask whether can we convert Revive Database table from MyISAM to InnoDB? As MyISAM is an older storage engine which affects the performance for following reasons : 1) MyISAM does the full-locking of the table. 2) MyISAM does not support referential integrity 3) MyISAM does not support Commit & Rollbacks After all these conditions if we convert the database to InnoDB will it affect the ad serving or it will stop working? Let me know your thoughts. Thanks Quote
andrewatfornax Posted March 26, 2018 Report Posted March 26, 2018 Should work just fine. As always, take a backup of your database (and check that it's a good backup that you can use to restore from if required) before you convert, but I've run Revive Adserver against InnoDB tables before. Quote
firstimpression Posted May 21, 2019 Report Posted May 21, 2019 Don't do this. https://github.com/revive-adserver/revive-adserver/issues/102 Even after 6 years of this discussion I want to confirm that InnoDB is still ridiculously slow with Revive when logging impressions at high frequency. Tried a lot of InnoDB settings, in the end reverted the "bkt" tables to MyISAM. I think ON DUPLICATE KEY UPDATE in all logging scripts causes a type of lock that makes all the mentioned InnoDB advantages useless. Quote
Fritex Posted January 2, 2022 Report Posted January 2, 2022 Thank you for feedback about InnoDB! Was thinking to switch to it, but seems I'd better stay with MyISAM at least with Revive AdServer. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.