[mythtv] mythconverg on RAM drive?

Steven Adeff adeffs.mythtv at gmail.com
Thu Aug 3 01:27:29 UTC 2006

On 8/2/06, Nigel Pearson <nigel at ind.tansu.com.au> wrote:
> > Has it ever been considered to store the mythconverg database
> > on a RAM drive with periodic updates to a harddrive for backup?
>         Lots of options have been considered.
> (most recent MySQL Lite - it wasn't faster!)
>         The main problem with something like this is that
> it removes functionality. A memory buffer is only
> easily accessible from the local machine, and MythTV
> is a client-server system. How will my slave backend
> and Mac laptop frontend access the RAM drive?
>         This would also be very hard to implement -
> there are SQL statements sprinkled through the code.
> Unless you were planning on keeping the SQL interface.
>         If you really want the database in RAM,
> there is probably a way of setting up MySQL to do that.
> Just move /var/lib/mysql (or similar) to /dev/ram0,
> restart MySQL, and do some testing.

Thanks Nigel, that was my idea, just moving /var/lib/mysql to RAM and
see how it goes. I'll wait a bit to see if anyone can think of a
reason why this may be a bad idea.

Before you ask, read the FAQ!
then search the Wiki, and this list,
Mailinglist etiquette -

More information about the mythtv-dev mailing list