studley;194512 Wrote: > is it key_buffer or key_buffer_size? It's key_buffer_size, but (I asked the question on a MySQL list) this option only affects the performance with MySAM tables. Since SlimServer uses InnoDB tables, this setting should have no affect on SlimServer performance.
Actually, unless you have a huge library, I don't expect any changes to made the MySQL parameters to have much affect on performance. The quantities of data, index sizes, etc. that SlimServer works with are quite small and I imagine that there's seldom more than two or three processes accessing the SlimServer database on most networks. I'd be willing to bet that a _much_ larger gain in performance could be had by switching to MyISAM tables and maybe getting rid of all the text/blob fields. I've updated my database to get rid of the text and blobs, changing them to varchar, but it didn't make a noticeable difference. I tried changing the InnoDB tables to MyISAM, but it's possible for only a couple of tables - the rest will throw constraint violations when you try to alter the tables. It might be possible with an empty database, so I might try that next. -- JJZolx Jim ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=32417 _______________________________________________ discuss mailing list [EMAIL PROTECTED] http://lists.slimdevices.com/lists/listinfo/discuss
