Jump to content

Can we convert Revive Database tables from MyISAM To InnoDB ?

Recommended Posts


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.


Link to comment
Share on other sites

  • 1 year later...

Don't do this.


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.

Link to comment
Share on other sites

  • 2 years later...

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.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...