- Moderator
- #71
A lot of files on a network drive. I now there are more than 1000.Every client now can access this (and normally did this during startup) so a sync is done semi- automatically once per run...
A lot of files on a network drive. I now there are more than 1000.Every client now can access this (and normally did this during startup) so a sync is done semi- automatically once per run...
Not more needed to use centralized SQLIte DB in MP1... But without any guarantee... Same is for Kodi, it is also without any support or named as "stable"...Added 3 lines in the configuration file
Maybe, but this function is a long time. And it works flawlessly. I do not know why it has not yet been carried to the settings. And have not removed the status of "advanced (complicated) and experimental" and replaced it with a stable.Same is for Kodi, it is also without any support or named as "stable"...
I added 350 files to a network folder and added some statistics rows to my dev build.
Here is my test result:
MySQL on remote: GUIVideoFiles:LoadDirectory is finished in 6060 ms
MySQL on local: GUIVideoFiles:LoadDirectory is finished in 2561 ms
SQLlite on remote share: GUIVideoFiles:LoadDirectory is finished in 2303 ms
SQLite on local: GUIVideoFiles:LoadDirectory is finished in 1302 ms
It means the MySQL is slower then SQLite but the big difference if the database is in remote.
Maybe on the server, which indexes to correct? Or where there is a bottleneck? Maybe it makes sense, take all possible data, and then it locally, from memory select?I can speed up the MySQL on remote: from 6 sec to 4-4.5 sec on same folder. This is not a big result but better than nothing.
Maybe on the server, which indexes to correct? Or where there is a bottleneck?
I mean that we should abandon the many small requests in favor of one big one. And then to process the data from it. At least when you open the plug-in, or entering into a new folder.The client caching is bad think because we want to use many clients at same time.