Slow TVGuide Listing - index optimizations possible?

[dreamwalker]

I imported a dish xml tv file that's ~170mb using mc2xm (gbpvr.db3 file is ~100mb)l. It seems to make gbpvr crawl at several points in the setup process, but more importantly, everytime I load gbpvr front end, it will take quite some time before the tvguide completely loads. Time to actual watchable content is about 2 minutes.

It seems like the tvguide is loading all days worth of data for 1 channel and then going to the next... Is it possible to load only today's content and go down and then the next days ?? I've used other EPG and gbpvr seems to have the slowest one out there.

Is there some sqlite profiling that can be done here? I'm thinking some changes to the indices might help. Does anyone know what sql is being run behind the scene so that I could tweak the guide myself ?

Thanks!

I'm running a P4p800 2ghz 1gb ram.

[carpeVideo]

You could try TV listings instead of guide - it tries to load what is visible first and then load the rest in the background.

[dreamwalker]

Already tried that... Still a little more sluggish than I'd expect, but it seems slightly faster... Is the source code for the TV Listing available somewhere?

[dreamwalker]

So I've been trying to figure out why my CPU is at 100% after coming out of standby. It seems like GBPVR restarts/reloads the tv guide from the database. This causes the cpu to spike to 100% for quite some time ( ~5 minutes). My HD video's then become jerky... Is there anyway to fix this?? I can't be the only one with a 100MB database loaded with programe data??

[sub]

So I've been trying to figure out why my CPU is at 100% after coming out of standby. It seems like GBPVR restarts/reloads the tv guide from the database. This causes the cpu to spike to 100% for quite some time ( ~5 minutes). My HD video's then become jerky... Is there anyway to fix this?? I can't be the only one with a 100MB database loaded with programe data??

The app loads the listings in the background when first started, and then proceeds to do some processing of those listings (in memory indexing, filling gaps etc). For the vast majority of people this completes in just few seconds. I've got about 40 channels, and weeks worth of listings, and it takes about 3 seconds to complete this background processing.

There has been some users that have reported it taking a couple of minutes, typically DishNetwork users with a few hundred TV channels and 14 days worth of listings. If you're one of these, the easiest fix is probably reducing the number of days of listings you retrieve, and getting rid of a pile of those channels that you know your never watch. This makes a huge difference to the number of entries the app has to pre-process, and will drastically cut the time required.

[dreamwalker]

OK, I'll try to clear out the db3 file and see if makes thing run smoother. Hopefully any gaps in the db won't have too much negative affect on gbpvr performance.

If all else fails, I'll have to figure out how to clean up the content result from mc2xml. I don't suppose there's an app there that will simplify this process (yapi2xml seemed kinda flaky and unreliable after some use).

[sub]

If all else fails, I'll have to figure out how to clean up the content result from mc2xml. I don't suppose there's an app there that will simplify this process (yapi2xml seemed kinda flaky and unreliable after some use).

Sorry, I dont know - I've never used either mc2xml or yapi2xml.

[bordr415]

On my 10 gigabit network it only takes a few seconds (about 4-5) to load the tv guide on startup. My laptop though takes about 3.5 minutes to load the guide. I'm not sure how to reduce the channels in mc2xml without doing it manually which would be a pain as it updates once every 3 days.

To Sub - Thanks for all the hard work!