[mythtv-users] Issues with 0.25
Michael T. Dean
mtdean at thirdcontact.com
Mon Feb 27 20:15:32 UTC 2012
On 02/27/2012 07:22 AM, Scott & Nicole Harris wrote:
>>> Not any help, but during my brief test period with 0.25, I too had to
>>> increase max_connections (from 50). I started at 100, but very quickly I
>>> reached 80% of that max with very little actually going on. I ended up
>>> having to bump it to 200 to feel safe.
>> At some point, the mysql default changed to 150 (a later
>> 5.1 release, I think), although if you specified an explicit
>> value, that would have been used instead.
> Yes, I changed it to 50, because it was adequate. I think the question
> is....why was 50 adequate under 0.24 and under 0.25 it is woefully
> inadequate? Prior to this 0.25 test, my max ever connection was 30ish.
> That's on a system with 3 HDHRs, up to 5 recordings going at once, 4
> commflags / transcodes allowed at once, 5 FEs and 2 BEs.
DB connection pooling was completely reworked in unstable due to
limitations (that we were ignoring until recently) in Qt API. We now
have multiple DB connection pools--one for each thread in MythTV (as is
required in Qt4+). There's probably room for "tightening up" our
current implementation, but nothing will be done about it before
0.25--this isn't a bug, but an opportunity for future optimizations.
You will need to configure your MySQL server appropriately for the
application's requirements.
Mike
More information about the mythtv-users
mailing list