[WiP] Centralised database in My Video, My Pictures and folder settings (1 Viewer)

[ajs]

How many files are in the folder where you see the differencing?

Cartoons folder ~200-250
Movies folder ~300-350

 

[regeszter]

How many files are in the folder where you see the differencing?

Cartoons folder ~200-250
Movies folder ~300-350

How many seconds needs to show the folder? Is it a local folder? Did you move the thumbnails from local machine?

 

[ajs]

How many seconds needs to show the folder?

Local database ~1-5s
MySQL databse ~3-15s

Is it a local folder?

No. Network share (Windows Home Server 2011)

Did you move the thumbnails from local machine?

No. If transfer directory of thumbnails, to the server (hardlink, so work on my computer 3) the speed of opening the folder is almost unchanged.

I do check on the test computer.

 

[regeszter]

How many seconds needs to show the folder?

Local database ~1-5s
MySQL databse ~3-15s

Is it a local folder?

No. Network share (Windows Home Server 2011)

Did you move the thumbnails from local machine?

No. If transfer directory of thumbnails, to the server (hardlink, so work on my computer 3) the speed of opening the folder is almost unchanged.

I do check on the test computer.

Where is the mysql server? On WSH or locally?

 

[ajs]

Where is the mysql server? On WSH or locally?

On WHS Kodi uses it as well.

 

[regeszter]

I will test it with 300 files in one folder.

 

[regeszter]

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.

 

[ajs]

It means the MySQL is slower then SQLite but the big difference if the database is in remote.

Why Kodi no such difference? Well, the local MySQL think very few people interesting. And it is strange that such a big difference in the local MuSKL and remote MySQL.

 

[Lehmden]

Hi.

It means the MySQL is slower then SQLite

We have encounter the same while developing SQLite DB plugin for MP2 server, so no big surprise. If you optimize SQLite for speed the difference even gets bigger (up to a factor of 4 means SQLite is four times as fast as MySQL when used as DB backend for MP2 server). So for MP2 there is an easy choice... But in this use-case you need to think about multiple write access at the same time, something SQLite did not like that much. MP2 server is handling all access to the DB, so no issue there, but in MP1 case you can not prevent simultaneous write access in all circumstances.

Why Kodi no such difference?

There also is a difference and this may be the reason why the centralized MySQL DB is no part of the regular Kodi release...
Due to the proper .nfo support a centralized DB is not that important for Kodi than it is for MP. Simply hit "save DB" in GUI and all metadata incl. watched status is saved near to the media. Every client now can access this (and normally did this during startup) so a sync is done semi- automatically once per run...

 

[ajs]

There also is a difference and this may be the reason why the centralized MySQL DB is no part of the regular Kodi release...

As no part? Added 3 lines in the configuration file and everything works out of the box.
Just not everyone is necessary, and Kodi is more adapted to the type of work: put the USB stick and see.

Due to the proper .nfo support a centralized DB is not that important for Kodi than it is for MP

I transferred the the database from MP in Kodi . Unload all NFO, and start the update library on Kodi .