2017-02-13, 18:51
Have your server and RPi got clocks set to the same time? Or maybe the MySQL-slow.log time is the end of the slowness while the kodi.log event would be at the begining.
Whatever, it is not GetAlbumsByWhere that calls the unplayed songs query - that is not in the code, and anyway it also reports that the query took 2247ms
I still suspect Xonfluence for calling unplayed songs, and for anyone with such a large lib it is a disaster to be querying all the songs randomly. But I am also shocked that MySQL takes so long to do the query, but I guess it is already busy with the scans loading. At least I can see you have 148206 songs scnned so far.
And the memory hang is just after? Do we know that for sure?
When you restart Kodi switch to Confluence skin before scanning.
Whatever, it is not GetAlbumsByWhere that calls the unplayed songs query - that is not in the code, and anyway it also reports that the query took 2247ms
I still suspect Xonfluence for calling unplayed songs, and for anyone with such a large lib it is a disaster to be querying all the songs randomly. But I am also shocked that MySQL takes so long to do the query, but I guess it is already busy with the scans loading. At least I can see you have 148206 songs scnned so far.
And the memory hang is just after? Do we know that for sure?
When you restart Kodi switch to Confluence skin before scanning.
