[mythtv-commits] Ticket #12016: Watching in progress recording stutters

MythTV noreply at mythtv.org
Mon Mar 17 05:15:06 UTC 2014

#12016: Watching in progress recording stutters
 Reporter:  angela.schmid@…            |          Owner:
     Type:  Bug Report - General       |         Status:  new
 Priority:  minor                      |      Milestone:  unknown
Component:  MythTV - Video Playback    |        Version:  0.27-fixes
 Severity:  medium                     |     Resolution:
 Keywords:  WatchingRecording stutter  |  Ticket locked:  0

Comment (by Steve Meyers <steve-mythtv@…>):

 Replying to [comment:18 angela.schmid@…]:
 > As MythTV only supports MYISAM, I still tried the following MySQL
 setting and everything was also OK:
 > innodb_flush_log_at_trx_commit = 0

 I tried this setting, and it worked for me, as well.  Changing the
 recordedseek table to MyISAM worked also.

 By default, InnoDB will flush transactions to disk when they are
 committed.  I'm not sure if it just flushes its own data, or all data that
 needs to be written to disk.  I believe it's the latter, since I don't
 believe Linux has a way to just flush your own data.  If that's the case,
 then it could be that it's forcing the MythTV stream to be written to disk
 before continuing.

 So in short, I don't believe MythTV is necessarily doing anything wrong,
 it's just a byproduct of how MySQL works.  Since the recordedseek table is
 not critical, I don't see any reason to use InnoDB for it.  It might make
 sense for MythTV to force that table to be MyISAM.

Ticket URL: <https://code.mythtv.org/trac/ticket/12016#comment:22>
MythTV <http://www.mythtv.org>
MythTV Media Center

More information about the mythtv-commits mailing list