Re: MySQL for CircleMUD Player Saves: Thoughts?
Sweetness. I switched all the mySQL tables back to myISAM from InnoDB and the irksome hiccup is gone!
Apparently, it takes a bit of experience to configure InnoDB well. I think the default settings flush the table to disk frequently, which may have caused that delay (the HD was scratching every time a player entered/left).
I think the player eq file losses happened when the MUD was young and unstable, and running under OSX. The OSX detail may be the relevant one because the server files were on an NTFS partition with open-source driver support for Darwin (MacFUSE). I haven't really had lost eq complaints since we migrated to Ubuntu. In any case, the player saves in my MUD are binary (as is the main player file) and badly need to go!
Onward to more SQL goodness.
|