[mythtv-users] my experience with myth on a solid state drive
adeffs.mythtv at gmail.com
Fri Jan 6 16:20:49 UTC 2012
On Fri, Jan 6, 2012 at 11:11 AM, Ronald Frazier <ron at ronfrazier.net> wrote:
> On Fri, Jan 6, 2012 at 9:31 AM, Steven Adeff <adeffs.mythtv at gmail.com> wrote:
>> So what your suggesting is to raise the value of both to a size that
>> will allow for these temporary tables to reside in memory, which as
>> Ronald suggests, is just over 500MB?
> To be clear, 500MB was about what I was seeing. Since this is all
> scheduling data, then it's going to depend on a number of factors,
> which may include things like the number of channels you have defined
> (more channels == more possible programs to compare), the number of
> recording rules, and possibly even things like the size of your
> recording history (not sure if any of this makes its way into temp
> tables or if it's accessed straight from the permanent tables).
> Your temporary tables might be 100MB, or they might be > 1GB. The way
> to tell is to monitor the /tmp folder while the scheduler is running.
> Open 2 windows. In one window, run the following:
> watch -n 1 du -sh /tmp
> In the other, run:
> mythbackend --resched
> And then watch in the first window to see how large it grows compared
> to the original size.
right, I should have been more clear in using that number since it's
what you used and so easier to reference what memory use I was
incidentally, my usage was also ~500MB when I used the same process
yesterday to check =D
Before you ask, read the FAQ!
then search the Wiki, and this list,
Mailinglist etiquette -
More information about the mythtv-users