[mythtv] mythconverg on RAM drive?

Chris Pinkham cpinkham at bc2va.org
Thu Aug 3 04:01:10 UTC 2006

* On Wed Aug 02, 2006 at 08:26:58PM -0600, David Snider wrote:
> 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...

This is more of a -users question, but if you want to test the effects
of something like this pretty easily, just run a command that will
push all the mysql data into the filesystem data cache.  Then run
a reschedule in myth and see if it sped up since the data was still
in cache.  If you watch the disk I/O during the reschedule, you
shouldn't see any disk activity related to loading the tables off
the disk if they were still in the cache.

A simple command like "cat /var/lib/mysql/mythconverg/* > /dev/null"
will seed the mythconverg database files into the cache.  How long
the data stays in there depends on your system, but it's good enough
for a quick test.

I think you'll find that more time is spent performing the actual
queries than reading data from the disk, so you might not be able
to save that much time relative to the total time queries or
reschedules take.


More information about the mythtv-dev mailing list