Possible scheduler performance enhancement

[Doug Haber <doug@…>]

I noticed that one of the queries in the scheduler was taking ~15 seconds for me and when I removed p.description it dropped down to ~1 second. I don't think that this particular description is actually used anywhere so changing it to "" increased my performance with no scheduling side effects (yet - I've only tested this for a few hours). Since all of my descriptions are < 255 another fix might be left(p.description, 255) or something similar.

See attached patch.

Thanks! D

[Doug Haber <doug@…>]

I did some testing last night and I was able to get almost the same performance increase by using:

left(p.description, 16000)

In this way no data is lost and users still get a performance boost.

-Doug

[gigem]

The description is used to check if two programs are the same when programids aren't available and It's also displayed to the user on the Upcoming Recordings screen, so removing it is incorrect. I do see a tiny speedup in my scheduler runs when using left(p.description, 16000), but my scheduler runs are short enough that the change is insignificant. Anyway, until someone can explain *why* this change makes a difference, I'm not inclined to apply it. The column length is already defined in the database schema, so I don't like programatically limiting it, even to the same length, in one single code path.