[mythtv] mythconverg on RAM drive?

[David Snider]

I'm just curious if anyone is experiencing enough disk IO contention  
to justify the risk.  My experience is that the database sits idle  
for quite a bit of time and there is very little IO...
On Aug 2, 2006, at 7:27 PM, Steven Adeff wrote:

> 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.
>
> -- 
> Steve
> Before you ask, read the FAQ!
> http://www.mythtv.org/wiki/index.php/Frequently_Asked_Questions
> then search the Wiki, and this list,
> http://www.gossamer-threads.com/lists/mythtv/
> Mailinglist etiquette -
> http://www.mythtv.org/wiki/index.php/Mailing_List_etiquette
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev