Slow import of EPG-Data

[driver140771]

Hello, i use Kodi 14.2 with the 1.9.13.1 Addon on my Rasperry-Pi2.

When i start the Client (Rasperry) the import of the EPG-Data is very slow (20s)

Is this a problem from the Addon?

I have tested this with the DVBViwer as server and the DVBViewer-Addon and it is twice faster!!!

Thank`s

[the_man]

How many channels do you have?

[driver140771]

76

[Oberon]

Is the amount of EPG data the same when you use DVBLink and DVBViewer?

[beeswax]

I've also noticed this. I'm using the exact same guide data as I was when I was running DVBViewer (EPGCollector has simply been reconfigured to run as a DVBLogic Plugin instead of injecting into DVBViewer). A full import of guide data when using DVBViewer takes only a few seconds and you can barely read the channel names as they whiz through so quickly (~100 channels). But with DVBLink, each channel name appears for about 0.5s making for a very slow import. The "Importing guide from clients" dialogue has actually become quite an annoyance as it partially obscures the view of the wall view if you're looking for a movie or TV show to watch.

Is this a shortcoming of the Kodi addon or the actual DVBLink Server? Is there anyway this can be sped up?

Related thread: http://forum.dvblogic.com/viewtopic.php?f=66&t=30738

[Oberon]

For how long in the future is dvbviewer data imported?

[beeswax]

7 days, that's all Sky supply when you pull the EPG data direct from the satellite. As I said, the amount of data and for which channels should be exactly the same, I didn't change my EPG Collector settings, simply switched from pumping the data into the DVBViewer Recording Service to acting as the DVBLogic EPG plugin. I always make sure to exclude any channels I'm not using in EPGCollector in order to keep the amount of data collected to a minimum. Unless you're aware of some difference in the way DVBLink utilises EPGCollector when used as a plugin?

If I view the guide in Kodi when using DVBiewer, I get the full 7 days for all channels. Just as I do with DVBLink, only difference is the amount of time it takes to import said data from the backend. I'm not sure how DVBViewer stores the EPG data once it's been received from EPGCollector. Maybe they store it in such a way that it can be accessed more quickly when a Kodi client asks for it? Or maybe their Kodi addon requests the data in a different way? Or maybe their service sends the data to Kodi in a more efficient manner?

edit: I'm just running some tests now, going to try and get Kodi debug logs to compare a DVBLink EPG import with a DVBViewer one, will take a few minutes.....

[beeswax]

Here are some Kodi logs with debugging enabled which shows the breakdown of how long each operation takes:

DVBLink log: https://dl.dropboxusercontent.com/u/14792018/Logs/dvblink.txt
DVBViewer log: https://dl.dropboxusercontent.com/u/14792018/Logs/dvbviewer.txt

As you can see, DVBLink takes 45 seconds from the moment the EPG database is cleared in Kodi. DVBViewer is done in 4 seconds. Hopefully these logs disclose somehow how they are doing it so quick?

edit: I should probably mention, all this testing is being done using the Kodi client (Jarvis final) on the same machine that's hosting DVBLink/Viewer. This machine has an i7 5820k so may be doing some of this quicker than the little i3 NUCs can.

[beeswax]

Does the above help at all?

[dvbGuy]

I see the same thing.

I used to use WMC and when the guide data was imported it took about 1/3 the time of DVBLink (same number of days and channels). And the WMC guide data included EPG images for the shows.

[Oberon]

We will be looking at it in the context of DVBLink v6 release.

[joshy123]

We will be looking at it in the context of DVBLink v6 release.

Hopefully it can be fixed, have 78 channels on dvblink and it takes more then double then it does for iptv simple client and tvheadend to import over 500 channels

[the_man]

At the test build we have fixed this issue. But no any ETA at the moment when the release version will be finished.

[beeswax]

Thanks for the update, looking forward to trying it out.

[beeswax]

Update: I've tested this with the v6 beta and my EPG update time is now down to 17 seconds - huge improvement.

There's still room for improvement I think but this has brought the time down enough for it not to be a nuisance any more. Oberon - do you think you can shave any more seconds off this?