You're ahead of me on this. My experience in the past has been on linux systems where I've had to manually create the empty slow query log file and give it the appropriate permissions so that mysqld could write to it. But that was several mysql versions ago and I'm not sure that's still necessary.
Your log is indicating poky response to the new music query, but nothing out of the ordinary. In the case of a Cartesian result set, you'd see a "rows examined" value in the MILLIONS rather than in the tens-of-thousands as in your log. So, I don't think there is anything inherently wrong with the query itself...it's just poky on your system for some reason. You've discovered the wonderful world of my.tt tweaking and you've found tweaks that seem to solve your problem. The only other thing I would suggest is this: if you really want to verify the bad performance of the new music query, you could stop SBS, completely delete the cache\mysql folder, defrag your hard disk, reboot your system, let SBS rebuild the database from scratch, reboot again and then test. I'd at least do that much before deciding that there's something fundamentally wrong with the design of the new music query. -- gharris999 ------------------------------------------------------------------------ gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115 View this thread: http://forums.slimdevices.com/showthread.php?t=73010 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
