Web Interface search impossibly slow - anyone else?

[littlalex]

Howdy all...I've happily upgraded from 96.13 to 99.5 but I'm having one problem with the web interface.

My searches for shows via the web interface (on my internal 100MB network) are impossibly slow! I'm talking two or three minutes for a result to return and I always do get the result.

The old version wasn't snappy, taking about 30 sec, or so and I'm running what
I consider a marginal system as my server (XP 1600+, 512 MB ram. W2K SP4)
but I'm thinking this is not about hardware. I'm thinking maybe DB corruption?
I did do the upgrade from ms access to SQL Lite.

Any one have a similar experience or any ideas?

Happy New Year in advance,
littlalex

[UncleJohnsBand]

Nothing has really changed in that area of the code for some time.....the speed of search results is directly connected to how much EPG data you store, how many channels you have available, how fast your GPBVR host PC CPU is and how much memory is available on that machine.

For example....say you have 100 channels....and are storing 12 days of EPG data. If you take an average of 48 1/2 hour shows available in a single day per channel....then multiply that by the number of channels....then take that by the number of days in the EPG....you can see there is a lot to pull back.....then the filter (search criteria is applied).

This is just a simplified example of what occurs with a search but shows that the more EPG data and Channels you have the larger the search base becomes:

48 show segments per channel per day * 100 channels = 4,800 shows per day

4,800 shows per day * 12 days = 57,600 shows that are returned for filtering

The search pulls back all EPG entries and then filters out the results that you see on the web page.

The network speed should not have that big of an impact since all the work is being done on the host PC.

The one big difference is that you are now using the .NET 2.0 framework....but for the most part the 2.0 framework provides better performance than the 1.1 framework.

[mikeneron]

I find the search to be rather slow as well, but it's something that I just deal with as the software is so awesome it's more of a minor inconvenience. I think mine has to do with the genres. There seems to be an issue with how those get displayed as there are about 50 of each genre in the list (ie. Action, Action, Action, Action, Action, etc). Is there a way to totally take out the Genre from the search function? I have never even used that before and I think that would solve my slow search problem.

[UncleJohnsBand]

This post by sub provides a way to remove all the Genre and then they will be rebuilt with the next EPG load.

As for search slowness have you calculated out how much info you are searching......number of channels * number of segments in a day (I use 48) * number of days loaded with your EPG load....

For example.....72 channels * 48 * 8 days EPG = 27,648 programmes that are searched for every search.

So amount of RAM on the machine, processor speed and disk speed all play into the overall performance.

The above search process stems from using the API rather than querying straight against the data tables themselves with the search criteria.

Hope this helps.

[mikeneron]

That is about a billion times faster...thanks!!! This makes it so much easier to do many searches in a row.

[UncleJohnsBand]

That is about a billion times faster...thanks!!! This makes it so much easier to do many searches in a row.

Cool.....glad to hear it.