EPG takes a long time to load

[sub]

What type of machine are your client and server?

Even on a slow machine you should be seeing the guide loading within a few seconds, but knowing what your devices are may give some more clues.

[koijh65]

It's faster. It does not instantly load like you said in post #6. It takes 20 - 30 seconds.

How many channels are in the Guide?

Please display the Guide and then attach logs telling us the time that you displayed the guide ... https://github.com/sub3/NextPVR/wiki/get-help ... Thanks.

46 channels

What type of machine are your client and server?

Even on a slow machine you should be seeing the guide loading within a few seconds, but knowing what your devices are may give some more clues.

CPU: i7 3632 4 cores/8 threads
RAM: 8GB 1600 MHz DDR3
SSD: Samsung 850 EVO SSD 540MB/s Seq. Read, 520MB/s Seq. Write

[sub]

Yeah that machine should fill in the guide pretty much instantly.

Any chance you can point your phone camera at it, and get a quick video so we can see it happening, and post the video somewhere so we can take a look? The way it's filling in might give some clues.

[Ludron]

It takes a long time to load the guide data on the TV Guide page. I have 46 channels. Version 4.x on the same hardware does not take long.

How long are we talking? Yes, it has to do a lot more for dynamically loading and displaying the guide data in the web app, so a bit slower than v4. You typically see the data load in (over half a second or so).

This is an entirely different sort of application to v4.x. It's not trying to be exactly the same in all aspects. The majority of stuff it does is a lot better than v4. There may be some areas where v4 had a slight edge (but at the same time was a lot more limited)

In some cases there may be similar issue when on both machines Internet is not available. 

What type of machine are your client and server?

It seems that any client(browser) will not display anything until timeout of 1.6-2min(attempt to load some bootstrap css from cloudflare which is not possible at some remote locations)

[sub]

It seems that any client(browser) will not display anything until timeout of 1.6-2min(attempt to load some bootstrap css from cloudflare which is not possible at some remote locations)

Which page did this? these css files it uses should be all locally included in the setup, without needing to hit cloudflare.

[Ludron]

It should be easy to reproduce on any isolated system on pages like /guide.html or /help.html

There should be some kind of button which can set Pi system date/time from EPG.(or we need to build NTP Server via GPS?)
trust no one?You should use at least three different external sources such as Galileo, DCF77, and GPS. That is: You should not only rely on the time codes of a single foreign country.

Code:

section_number 72, last_section_number 248

No need to wait 60s? Move on after last expected section?

[sub]

Code:

section_number 72, last_section_number 248

No need to wait 60s? Move on after last expected section?

It's actually not quite that straight forward. These section numbers are per table, and per service.

Depending on the type of tuner you're using, it does already move on when it's got all the data. ie, HDHR and SAT>IP tuners move on to the next frequency when it's got the complete set of DVB EPG data. The same logic hasn't yet been added to regular DVB tuners.

[sub]

It should be easy to reproduce on any isolated system on pages like /guide.html or /help.html

This is fixed for the next build.

On the guide page, one css file was accidentally referencing cloudflare, even though we had the file available locally.

On the help page, there was a couple of urls I removed that weren't needed.