<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Feb 21, 2015 at 5:16 AM, Roger Heflin <span dir="ltr"><<a href="mailto:rogerheflin@gmail.com" target="_blank">rogerheflin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><div class=""><div>
On Fri, Feb 20, 2015 at 12:53 PM, Hika van den Hoven <<a href="mailto:hikavdh@gmail.com">hikavdh@gmail.com</a>> wrote:<br>
> Hoi James,<br>
><br>
> Friday, February 20, 2015, 7:32:27 PM, you wrote:<br>
><br>
>> On Fri, 20 Feb 2015, Hika van den Hoven wrote:<br>
><br>
>>> I don't know how powerful those devices are, but I do all my<br>
>>> transcoding on my normal (6 core athlon) desktop machine even though<br>
>>> my backend (dual core) could probably do it too. I can with no problem<br>
>>> do 4 transcodings at the same time and stil work uninterrupted.<br>
>>> Just have a slave backend running on the machine you want to use for<br>
>>> transcoding and disable transcoding on the master.<br>
><br>
>> Thanks for your reply, Hika. It sounds like you're describing a scenario<br>
>> where the front and back ends are separated, right? If so, I'd like to<br>
>> keep the combination FE/BE set-up I have, which is why I was asking about<br>
>> whether the ECS hardware would be up to the task of rescaling while<br>
>> simultaneously recording. It seems possible it might be, since the ECS<br>
>> system Dave described was said to be a combination FE/BE, like mine. Just<br>
>> was hoping to get a clarification from him (or someone else) on that<br>
>> before looking further into this option.<br>
>> _______________________________________________<br>
><br>
> Yes, mine are separated, but also when combined you can delegate tasks<br>
> to a slave backend, on a computer that you normally use for other<br>
> things. That's the nice thing of how mythtv is set up and the fact<br>
> that all your computers are linked through the network. You could have<br>
> six backends and only one frontend on one of those backends or only<br>
> one combined one etc., etc.<br>
><br>
><br>
> Tot mails,<br>
> Hika mailto:<a href="mailto:hikavdh@gmail.com">hikavdh@gmail.com</a><br><br>I have an FM2 processor and the AM1's appear to have similar video hw.<br>
My fm2 does appear to do most of the hard work in the GPU. I<br>
have an old nvidia ion, an ecs liva, and a fm2 combined FE/BE. The<br>
FM2 is nice as the full sized board has 8 AMD supplied sata ports that<br>
appear to work flawlessly. With a high grade green power supply<br>
mine does not appear to be that power hungry. And the cpus are<br>
powerful enough that I can also transcode things to codec's that use<br>
considerably space.<br>
<br> </div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div>
<br></div></div></blockquote></div><br><br></div><div class="gmail_extra">Yep, when you go for REALLY-low-power systems, things get... interesting. :-) Trickier to set up, but rewarding when finished.<br><br><br></div><div class="gmail_extra">Before I made my LIVA a BE+FE combo, I was running it as a frontend only, to a backend machine which had an Intel Celeron 1037U processor (my previous FE+BE machine). The 1037U has about twice the performance of the N2807 in benchmarks, and with a 17W TDP, was quite low power as well. Nowhere close to the 4.3W N2807, but still just a fraction of the desktop class machine it replaced.<br><br>However, when I took apart the 1037U machine and transferred the database, tuners, and hard drive over to the LIVA and brought it back up as a FE+BE combo, it was noticeably more responsive and pleasant to use than the two separate systems... even though those two together had THREE TIMES the processing power of the LIVA on its own. The network transferring was the weak link. So adding a machine and splitting functions doesn't "always" make things better. :-)<br><br></div><div class="gmail_extra">On my LIVA, I did encounter problems when doing multiple recordings while commercial flag jobs were running. Restricting the commercial flagging to run in an overnight non-prime time slot easily solved that, and so far for my usage, it hasn't ever had a problem getting through them. A worthwhile tradeoff for me.<br></div><div class="gmail_extra"><br><br></div><div class="gmail_extra">Another example: On the 1037U system, I did some experimenting with using a Broadcom "Crystal HD" mini PCIe card for the heavy lifting of the video decoding. It turned out that while it worked (70%+ reduction in CPU usage and clocking down from the decode offload), the overall power consumption for the system had actually risen slightly when playing video content. So... saving power that way didn't quite work, even though on paper it looked like a good idea.<br><br><br></div><div class="gmail_extra">It's also worth noting that there are diminishing returns. Like I mentioned earlier, with the LIVA, it's so low power that your storage drive(s) will likely consume more power than your computing box. So you start looking elsewhere... I spent $27 and dropped another 5 watts of "always on" power usage by upgrading my old wireless router... something no amount of optimization would be able to do anymore with my always-on MythTV box. <br></div><div class="gmail_extra"><br><br></div><div class="gmail_extra">Deciding what to have sleep and what to have wake up is another challenge. Some do scripted shutdown/wakeup on FE/BE boxes, others leave them running to be available for other purposes (AirPlay target, UPnP media server, etc.). Some have an always-on backend but use a sleep/wake-on-demand frontend. Some feel like 65 watts at idle isn't worth it to bother shutting down, some cringe at the thought of 65 watts at LOAD, and some feel like 150+ watts at load is OK because it's shut down when not in use. Some live off the grid, and some live in cold climates with cheap electricity and use their MythTV machines as space heaters. Everyone has a different opinion and different priorities. :-)<br><br></div><div class="gmail_extra">- Dave<br></div><div class="gmail_extra"><br></div></div>