<div class="gmail_quote">On Wed, Oct 13, 2010 at 3:44 PM, Robert McNamara <span dir="ltr"><<a href="mailto:robert.mcnamara@gmail.com">robert.mcnamara@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">The original reporter's hardware was manufactured before the first</div>
public release of MythTV. My tongue in cheek answer was meant to<br>
explain that given my informal knowledge of myself and the rest of the<br>
devs, function and features trump making Myth work with decade-old<br>
hardware or plug systems. I just don't see any point in the future<br>
where making Myth run acceptably on a sheevaplug, or a P3/900 is even<br>
remotely a priority.<br></blockquote><div><br></div><div>I see no reason that an interested person couldn't look into profiling the weak points in the backend code, though. If you want to use that P3/900 for a frontend, all bets are off, but for backend ONLY... there may be some chance, but someone will need to do the hard work of finding the issues. We just aren't focused on enabling toasters to run as backends. If you guys want to put in the work, there are some of us that would be receptive to working with you to make things more efficient where possible. However, we aren't likely to take the time to find the bottlenecks for you, nor are we able to for every configuration.</div>
<div><br></div><div>The original poster needs to clarify what exactly this box is doing (as both Mike and I have pointed out already) to get any kind of sane answer to his underlying problem. Meanwhile, upgrading really will fix the issues :)</div>
<div> </div><div>It is also possibly a lack of RAM issue. If that poor box is running in swap, yer asking for pain.</div></div>