[mythtv-users] Slow MySQL query after delete

Larry K lunchtimelarry at gmail.com
Sat Nov 24 04:27:50 UTC 2007

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?

On 9/6/07, crs23 <pvr at groundhog.pair.com> wrote:
> Michael T. Dean wrote:
> >
> > I don't think much testing has been done on systems having identical
> > recording rules.  Though it shouldn't cause issues, cleaning out the
> > duplicates (triplicates?  whatever) would significantly simplify the
> > query's processing, so doing so would be very much to your advantage.
> >
> Done and the improvement was substantial.  There were several multiple
> entries.  One program had about a dozen duplicate entries and that just
> happened to be the program with the most previously recorded episodes.  I
> also changed the recordings to be on a particular channel instead of any
> channel which I think helped to.
> I'm now down to ~150,000 rows examined in 5.5 seconds, 696 rows
> returned.  5
> or 6 seconds is hugely better but still a bit of an annoyance.  But I'm
> very
> pleased with the results so far and the incredible support I've received
> on
> this forum.  Thank you to everyone!
> --
> View this message in context:
> http://www.nabble.com/Slow-MySQL-query-after-delete-tf4366877s15552.html#a12534738
> Sent from the mythtv-users mailing list archive at Nabble.com.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20071123/292075c2/attachment.htm 

More information about the mythtv-users mailing list