I just made the same changes to my.tt (in Windows under Program Files\SlimServer\Server\MySQL):
key_buffer_size = 32M table_cache = 256 sort_buffer_size = 4M read_buffer_size = 1M Added variables: innodb_buffer_pool_size = 64M I don't know how to run the MySQL admin tool so I don't know if the innodb_buffer_pool_size worked or not. However I did put spaces around the "=" having run into other parsers that would barf on an equal sign without spaces. Results: Browsing by Genre, Artist, etc. is AT LEAST three times as fast. A number of actions (pulling up the 100 albums in folk genre) are at least 10x faster. This is for a small (230 album, soon to be 400) flac collection (properly tagged) which really should have been easy for SlimServer to handle. I had thought the speed issues I was seeing were related to using the browser control of Slim Server, but it looks like most of the problems were with MySQL and/or with how SlimServer is using MySQL. Looks like at a minimum new versions of SlimServer should write out a different my.tt then they currently are, and the current SQL queries, joins, etc. should be examined for how expensive they are. I assume somebody has entered a bug on this? -- Tarn ------------------------------------------------------------------------ Tarn's Profile: http://forums.slimdevices.com/member.php?userid=7414 View this thread: http://forums.slimdevices.com/showthread.php?t=32417 _______________________________________________ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
