Brendan Hoar: > The 1660 patch points at the mythtv 0.20 possibility of a single thread > being responsible for regular reads from the ivtv mpg buffer as well as > having the potential to be suspended waiting for a very long database > query to return. That seems like a bad design. Yowch. If so, that is really a very stupid idea. Database queries need to be in a different thread(*); it's not as if the mysql backend isn't using threads already anyway. * they wouldn't HAVE to be if the MySQL people would get the idea that a properly designed async database library is a good thing to have. Oh well.
I disagree MySQL could have anything to do with this issue. Unless there is something very wrong with the version of MySQL in knoppmyth R5E50 (compared with the one in R5A16). I have a dedicated box as master backend with 3 encoders and another as slave backend with one. I did not have issues like these until I upgraded to MythTV 0.20, ivtv 0.8.x at the end of last year (same hardware, just added gigabit ethernets and disk space). IMHO, something that changed between versions 0.16 and 0.20 of Mythtv and/or versions 0.4.x and 0.8.x of IVTV is causing this.
_______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
