id summary reporter owner description type status priority milestone component version severity resolution keywords cc mlocked 10023 Improve performance of time search dekarl@… Karl Egly "The SQL query for time search takes 2 minutes over here. By slightly refactoring the query that can be brought down to 2 seconds. Just factor out the description column into a superquery with the actual query being a subquery. The new query looks like: {{{ select program.description, sub.* from program, ( SELECT DISTINCT program.chanid, ... here is the old query but without the description column ... ) as sub where program.chanid=sub.chanid and program.starttime=sub.starttime; }}} The reason for the difference is each description taking 48kb of memory no matter how much of that is actually used leading to the whole joining and sorting being done on the hard disk because it doesn't fit into the memory buffer. (at least that's what I suspect)" Bug Report - General closed minor 0.26.1 MythTV - General Master Head medium fixed 0