I have two Windows machines that are showing the behavior of pegging the CPU at 100% on the mysqld processes after the file discovery phase, when using 7.5 embedded and selecting MySQL. I have disabled antivirus software and re-run the tests, same result.
I'm trying to find out which query is that could be so expensive to run. My current guess is the following one (from http://svn.slimdevices.com/slim/7.5/branches/embedded/server/Slim/Utils/Scanner/Local.pm?revision=29935&view=co ) Code: -------------------- # 3. Files that have changed mtime or size. # XXX can this query be optimized more? my $changedOnlySQL = qq{ SELECT scanned_files.url FROM scanned_files JOIN tracks ON ( scanned_files.url = tracks.url AND ( scanned_files.timestamp != tracks.timestamp OR scanned_files.filesize != tracks.filesize ) AND tracks.content_type != 'dir' ) WHERE scanned_files.url LIKE '$basedir%' }; -------------------- Am I right? Anyone else see this behavior? -- dsdreamer ---------------------- "Dreamer, easy in the chair that really fits you..." ------------------------------------------------------------------------ dsdreamer's Profile: http://forums.slimdevices.com/member.php?userid=12588 View this thread: http://forums.slimdevices.com/showthread.php?t=74700 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
