FYI: When you update to v2020.11.24.2138, your guide database will be deleted and recreated.
The new database backend offers reduced disk space usage and better performance. On my test DVR I saw disk usage decrease by up to 27%
This should be a seamless change and most users will not notice anything different.
Is this an upgrade to the Channels DVR player? My Beta version will only update to version 11-20-2351.
No, this is for the server where the guide database is stored.
I upgraded and before the upgrade my guide was using 169MB. Immediately afterward the usage went to about 144MB. Today it’s at 199MB. I don’t care about the disk space at all. I haven’t added or changed sources since the upgrade so I wouldn’t expect to see an increase.
Just thought I’d let you know that for me there is actually an increase in disk usage.
am i the only one who thinks this seems to have slowed things down, not helped speed them up? my web guide is insanely slow lately, and i don't remember it ever being this way prior to this update...
Are you sure isn't slower because you've added hundreds more channels via pluto and other m3us?
It would help if you can check the browser network console and see which requests are slow and how long they take.
After some more investigation, it looks like the guide upgrade in v2020.11.24.2138 did not fully kick-in. It was stuck in a compatibility mode and not using the new improvements.
With v2020.12.12.0204 the guide database will again be automatically deleted/recreated, and the size/disk optimizations will take effect.
I haven't really added that many channels. the only custom ones I have are pluto...the rest are just the normal TVE channels (they're coming from the other channels instance rather than built in, but there aren't that any more actual channels than before except for pluto)...
next time I'm in front of a computer I'll look at the dev tools and see where the hang up is and let you know.
this seems to have helped. it took me from 8+ seconds to load the web guide down under 4 sec.
i take it back...seems it was only that fast because it didn't load practically any of the guide (the only thing it did load was locast). when i did a full delete/recreate, now it's taking even longer than before (7.42 seconds timed with a stopwatch from the time i hit guide to the time it finished loading).
the spot it seems to be slowing up in the dev tools is where it grabs all the logos.
@tmm1 any ideas on this? it's most certainly NOT faster, at least not for me. i was sitting in the drive thru today at popeyes watching in my tesla and it literally took 10-15 seconds to bring up the guide. happy to provide anything you need to troubleshoot, but something definitely is not working right if this was supposed to make things faster...
The DVR http log shows exactly how long each request is taking. What does it show for the guide data?
It could be that xmltv sources are slower. Or it could be the browser struggling with lots of images to load. The browser console shows requests times and a waterfall which can be used to pinpoint which request is holding up the page.
I have not noticed any difference on my dvr. The backend change here is a minor optimization that's very unlikely to be causing whatever you're seeing.
My guide loads in 300 milliseconds:
2020/12/20 18:34:33.972639 [HTTP] | 200 | 318.148334ms | 10.0.1.26 | GET "/devices/ANY/guide"
it's definitely the logos. it just sits there and spins and then all the logos appear in dev tools all at once...it took just under 10 seconds to load completely just now. if i change to only load favorites (of which i only have 5), it loads fast.
what doesn't make sense to me is how yours is loading so quickly and mine is taking forever. the only extra stuff i have loaded is pluto and about ten 24/7 channels from my own media...other than that, it's nothing different than using channels own sources.
If it's just the logos, it sounds like it might be a DNS resolution issue. What does your your DVR server have as its resolv.conf or equivalent, or which DNS servers are you using/superseding? If that is the root of your problem, then that's a network issue, and not a Channels issue.
After you observe this behavior, please go to Help -> Submit Diagnostic Logs from the web interface of the DVR and let us know when it's been submitted so we can have a better idea of what was going on.
done, just now.
Logs have been submitted as cd029039-39e7-4e45-86b2-47a8c40bc2a5. Please send an email to [email protected] to give details about the issue you're having.
that doesn't seem likely, considering it's super fast when only loading a few channels (like my favorites). if it were the DNS timing out or taking forever, it'd be slow no matter how many channels it was loading.
Are you still seeing this behavior when you reload or was it a one time thing? I don't see that sort of delay visible in the HTTP logs.
yep, still seeing it all the time, except when i switch it to a channel list that only has a limited number of channels. i wonder if it's pluto that is taking a long time to return the logos, but then someone else would have had to see this at some point...