[mythtv-commits] Ticket #9792: Deadlocked scheduler
MythTV
noreply at mythtv.org
Fri May 27 18:48:16 UTC 2011
#9792: Deadlocked scheduler
-----------------------------------+----------------------------
Reporter: warped <warpme@…> | Owner:
Type: Bug Report - General | Status: new
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: Trunk Head
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-----------------------------------+----------------------------
Comment (by warped <warpme@…>):
Well,[[BR]]
Week ago I do backup,delete,create,restore DB. I'm not sure also move I to
default mysql settings at that time or earlier. Anyway - since week I was
on my.cfg from arch package).[[BR]]
Week of stressing (45-50 rec. per day; alot of TV zapping with LiveTV) -
all was OK. Today I was ready to put comment on this ticket that issue
resolved.[[BR]]
3h ago I compiled latest HEAD (g62d7084), install and also decide to tune
DB by mysqltuner.pl script. Following changes are added into
my.conf:[[BR]]
changed table_open_cache 64->192[[BR]]
added query_cache_size = 12M[[BR]]
added query_cache_type = 1[[BR]]
added join_buffer_size = 384k[[BR]]
added tmp_table_size = 24M[[BR]]
added max_heap_table_size = 24M[[BR]]
added thread_cache_size = 8[[BR]]
Tuning gives mysqltuner.pl output like attached file. (also output on
default settings is attached).
After tuning DB tuning i.e. sched time was reduced from 83sec to 23sec.
Refreshing rec. UI is really faster with tuned DB.[[BR]]
1h I was really sad to discover deadlock again. Trace attached.[[BR]]
Hmm - first what comes to mind is tuning impact. Is it possible that this
is DB bug ?
--
Ticket URL: <http://code.mythtv.org/trac/ticket/9792#comment:4>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list