2013-05-26, 15:01
I have the same problem, after analyzing some SQL queries I came to the conclusion that the view "albumview" is significantly slower than the rest of the views, see http://pastebin.com/wyPhLkAe for the explain statement results.
The view "albumview" took 1,6 seconds to finish, the rest (artistview, songview) is much faster.
If I execute the statement in the view as a standalone SQL query, it is fast:
http://pastebin.com/iWmHSHSE
As you can see, the query is build of differently. Unfortunately I am no database expert so I don't know how to optimize this for local testing purposes.
I read somewhere that maybe the GROUP BY could be a problem.
Ialso removed the LEFT JOIN with the "song" database and it was faster, it took only 0.33 seconds. But I don't know if the
Maybe these queries can be optimized? Everything regarding "albums" in XBMC is really slow for me when using MySQL on a Synology DiskStation.
The view "albumview" took 1,6 seconds to finish, the rest (artistview, songview) is much faster.
If I execute the statement in the view as a standalone SQL query, it is fast:
http://pastebin.com/iWmHSHSE
As you can see, the query is build of differently. Unfortunately I am no database expert so I don't know how to optimize this for local testing purposes.
I read somewhere that maybe the GROUP BY could be a problem.
Ialso removed the LEFT JOIN with the "song" database and it was faster, it took only 0.33 seconds. But I don't know if the
Quote:"min(`song`.`iTimesPlayed`) AS `iTimesPlayed`"part is needed somewhere in the album view.
Maybe these queries can be optimized? Everything regarding "albums" in XBMC is really slow for me when using MySQL on a Synology DiskStation.
