I have a site using threads and several other apps that all access member data. However the myISAM tables turn into a dog's dinner when they all try to read data at once (update even worse) due to unexpected conflicts, timeouts and retries by each of the apps.<br /><br />I see some people are using InnoDB tables to hold membership information. Has anyone had this running in busy production environments? Have there been any problems? Were any mods required to the threads code?<br /><br />Thanks

No changes to the code are required if you don't want to use transactions.<br />We ran our production board for a few days with InnoDB, but it needs significantly more memory than MyIsam, so we switched it back.