Hmm
It occured to me recently that maybe one of the main weakness of how I designed the Kanji Koohii database, could be that I use a lot of MyISAM tables.
When I created the site many years ago, it was said that MyISAM was the faster choice. However a lot of time passed since then, and now I read:
MyISAM is optimized for environments with heavy read operations, and few writes, or none at all.
This would be good for the kanji table itself which is just a reference. However for much of everything else, such as the story votes, stories, flashcards... maybe it was a very bad choice.
Anyone with SQL experience? I am considering upgrading a lot of tables to InnoDB. Perhaps this would solve the really slow Story page queries. Any thoughts?
It occured to me recently that maybe one of the main weakness of how I designed the Kanji Koohii database, could be that I use a lot of MyISAM tables.
When I created the site many years ago, it was said that MyISAM was the faster choice. However a lot of time passed since then, and now I read:
MyISAM is optimized for environments with heavy read operations, and few writes, or none at all.
This would be good for the kanji table itself which is just a reference. However for much of everything else, such as the story votes, stories, flashcards... maybe it was a very bad choice.
Anyone with SQL experience? I am considering upgrading a lot of tables to InnoDB. Perhaps this would solve the really slow Story page queries. Any thoughts?
Edited: 2016-01-08, 11:07 am