EPG guide sluggish on pc client

[Gustovier]

Has anybody noticed the EPG guide sluggish on their pc clients(building a windows one)? I get better performance on my hd300s (and of course on the local server). I've been having issues getting phoenix to install properly on the client (still working through) but once it's up I definitely notice this lag.

[stuckless]

Originally Posted by Gustovier

Has anybody noticed the EPG guide sluggish on their pc clients(building a windows one)? I get better performance on my hd300s (and of course on the local server). I've been having issues getting phoenix to install properly on the client (still working through) but once it's up I definitely notice this lag.

It might be that the client is rebuilding the required images and caching them locally. On the server this may have happened once, but then other extenders reap the benefits of the images being scaled and cached. Clients are completely separate, so they'll need to build their own caches.

Or.. it could be a side effect of how Phoenix was installed... ie, not using the plugin manager

[Gustovier]

It looks like my CPU usage goes up considerably as I maneuver around the EPG

[sflamm]

it seems like the EPG does rebuild the cache. once you move around a little it become fast again (not sure why the client can't use the server cache just like you can leverage a central fanart store). perhaps this is possible?

[Gustovier]

Hmmm. I wonder if I can copy over the cache directory from the server to the client and it take advantage of it. Or would the hash mapping that identifies the files In the cache very from machine to machine thus making the cache only valid on 1 machine.

[stuckless]

Originally Posted by Gustovier

It looks like my CPU usage goes up considerably as I maneuver around the EPG

That is probably the on the fly image scaling that is causing that (ie populating the cache)

Originally Posted by sflamm

it seems like the EPG does rebuild the cache. once you move around a little it become fast again (not sure why the client can't use the server cache just like you can leverage a central fanart store). perhaps this is possible?

This could be possible, but the network latency may cause other issues, and not 100% sure we can share caches.

Originally Posted by Gustovier

Hmmm. I wonder if I can copy over the cache directory from the server to the client and it take advantage of it. Or would the hash mapping that identifies the files In the cache very from machine to machine thus making the cache only valid on 1 machine.

My gut feeling is that this would not work... I'm not 100% sure, since I didn't build the UI, but the hashes are probably difference for clients vs extenders, depending on the required sizes of the images. But you can certainly try and see what happens.

[sflamm]

That is probably the on the fly image scaling that is causing that (ie populating the cache)

The logos are very small - I doubt that scaling them can have much effect.
What else is being scaled? (and can it be turned off)

In general do you have some recommendations on improving the speed for Phoenix moving around?

I have also noticed that there can be a substantial delay when on 'stop' (particular to Phoenix). Is there a way to improve that?

[Gustovier]

Yeah I think it's something else. The standard stv guide
Navigation is very fast on my windows clients

Sflamm, unfortunately the devs that handle a lot
Of the Phoenix stv work don't come around to much anymore. The STV coding language is really really unique and has a significant learning curve. otherwise it might be easier to look into these things ourselves.

[sflamm]

I know Sean tries to do his best... but it is a lot of work to maintain and with other priorities. Phoenix is still the best all around STV in my opinion - it would be awesome if these quirks got ironed out.