2017-06-30, 11:20 PM
I'm running Kodi on a Raspberry Pi and upgraded from Jarvis to Krypton earlier this year. The first thing I noticed when booting Krypton was that it took a lot longer to process the NextPVR channels/EPG/recordings than Jarvis. Jarvis boots in well under a minute while Krypton takes nearly 2.5 minutes to boot.
I created debug logs for both systems and then wrote a Kodi Log Comparison Utility in Python to analyze my Jarvis/Krypton logs. My analysis appears to show that the EPG scraper (TVDB) may be the source of the slow boot problem. Take a look at the following log: https://pastebin.com/qrhfCZg9
My log shows the time differential between Jarvis and Krypton for each log entry. This analysis has confirmed my original observation that Krypton takes 2:18 longer to process the same number of channels during boot up.
Please note that the log report in my paste bin only shows the "EPG - UpdateFromScraper" event. I suspect that somehow the TVDB addon may be the source of the problem since it is apparently used to update the EPG for each channel. If this addon is the reason for the longer Krypton boot, the next question has to be what has changed in TVDB to cause this problem.
Has anyone else experienced a similar problem booting NextPVR?
I created debug logs for both systems and then wrote a Kodi Log Comparison Utility in Python to analyze my Jarvis/Krypton logs. My analysis appears to show that the EPG scraper (TVDB) may be the source of the slow boot problem. Take a look at the following log: https://pastebin.com/qrhfCZg9
My log shows the time differential between Jarvis and Krypton for each log entry. This analysis has confirmed my original observation that Krypton takes 2:18 longer to process the same number of channels during boot up.
Please note that the log report in my paste bin only shows the "EPG - UpdateFromScraper" event. I suspect that somehow the TVDB addon may be the source of the problem since it is apparently used to update the EPG for each channel. If this addon is the reason for the longer Krypton boot, the next question has to be what has changed in TVDB to cause this problem.
Has anyone else experienced a similar problem booting NextPVR?
