[mythtv-users] Is 4GB RAM overkill for mythtv?

Chad masterclc at gmail.com
Mon Feb 25 21:26:19 UTC 2008


[snip all kinds of great informatio]

>  InnoDB also buys you an extra advantage. The innodb_buffer_pool
>  variables lets you allocate memory to be used both both indexes *and*
>  data, so with appropriate tuning you can guarantee that data is always
>  sitting in memory and never flushed out of the pagecache.
>
>  This mail is long enough however, so I won't go into converting over to
>  InnoDB. I'm also not sure what the MythTV devs viewpoint on InnoDB is,
>  however it appears to work fine for me(~6 months now). If I get time
>  I'll try to put something in the Wiki about doing the conversion.
>
>  Matt

A wiki page would be very appreciated!  Also, if it truly isn't a
"problem" per se for MythTV, maybe you could supply a patch to trac
that changes MythTV to innodb by default (and provides a conversion
path via a perl script?)?

Thanks for the wisdom above!

-Chad


More information about the mythtv-users mailing list