What was your method to determine the duplicates? And did you simply issue a SQL delete to get rid of them, or some other mechanism?<br><br><div><span class="gmail_quote">On 9/6/07, <b class="gmail_sendername">crs23</b> <
<a href="mailto:pvr@groundhog.pair.com">pvr@groundhog.pair.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>
Michael T. Dean wrote:<br>><br>> I don't think much testing has been done on systems having identical<br>> recording rules. Though it shouldn't cause issues, cleaning out the<br>> duplicates (triplicates? whatever) would significantly simplify the
<br>> query's processing, so doing so would be very much to your advantage.<br>><br><br>Done and the improvement was substantial. There were several multiple<br>entries. One program had about a dozen duplicate entries and that just
<br>happened to be the program with the most previously recorded episodes. I<br>also changed the recordings to be on a particular channel instead of any<br>channel which I think helped to.<br><br>I'm now down to ~150,000 rows examined in
5.5 seconds, 696 rows returned. 5<br>or 6 seconds is hugely better but still a bit of an annoyance. But I'm very<br>pleased with the results so far and the incredible support I've received on<br>this forum. Thank you to everyone!
<br><br>--<br>View this message in context: <a href="http://www.nabble.com/Slow-MySQL-query-after-delete-tf4366877s15552.html#a12534738">http://www.nabble.com/Slow-MySQL-query-after-delete-tf4366877s15552.html#a12534738</a>
<br>Sent from the mythtv-users mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br><br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">
mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div><br>