[mythtv-users] HowTo tune MySQL for schedule time and in general?

David Engel david at istwok.net
Mon May 6 14:26:00 UTC 2013


On Sun, May 05, 2013 at 12:44:31PM +0200, Thomas Börkel wrote:
> On 05.05.2013 05:27, David Engel wrote:
> 
> > Something doesn't add up here.
> > 
> > In your first timing, the majority of time (5.88s) was spent in the
> > place phase.  That phase shouldn't be affected that much by DB
> > changes.  To get a later run in the 0.2s range, the place phase would
> > have had to sped up a lot and I can't see that happening with just a
> > DB change.  It is the match and check phases that are DB sensitive.
> 
> Only thing I can say is that the scheduler always took these long times
> before my changes and now it is always fast.
> 
> > In addition, the scheduler normally only runs the match and check
> > phases on things that might have changed.  That means you can't
> > arbitrarily pick scheduler runs and compare them because they might
> > not have done the same amount of work.  You can compare runs initiated
> > with "mythutil --resched" because those cause the scheduler to re-run
> > everything.  You can also compare runs by making a do-nothing change
> > to a single recording rule because those cause the scheduler to only
> > re-run the parts for that rule.
> 
> I compared the times by scheduling a new non-conflict recording and then
> deleting it again.

That sounds like a reasonable test.  Still, that amount of improvement
sounds way too good to be true.  If it works, though, enjoy. :)

David
-- 
David Engel
david at istwok.net


More information about the mythtv-users mailing list