<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hoi Joseph,<br>
<div><div class="h5"><br>
Thursday, September 11, 2014, 11:21:25 PM, you wrote:<br>
<br>
>> I have a little question about it. I have a ION board frontend and the<br>
>> backend in the same place, is it a good idea to join both frontend and<br>
>> backend in the same machine? This CPU could manage both service very<br>
>> good, I could add a dedicated GPU.<br>
<br>
> I would keep the frontend separate. You are bound to do things with<br>
> the backend that are likely to generate heat and noise and be disruptive<br>
> to your playback environment.<br>
<br>
> If the backend is somewhere else entirely, you can let loose with it<br>
> and do whatever you want.<br>
<br>
<br>
<br>
<br>
> He said that he has the backend and frontend in the same place...<br>
> he wasn't proposing to move the backend elsewhere. If the backend<br>
> is going to be there anyway, why have a separate frontend right next to it... just combine them.<br>
<br>
</div></div>While his machine should be powerful enough to do both I don't like<br>
them to be in the same machine. </blockquote><div><br></div><div>I respect your opinion, and while we all wish we had unlimited resources where we could dedicate a computer to single purpose, you must admit it is a bit wasteful.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Mythfrontend can sometimes be unstable<br>
needing a reboot. If the backend is in there you have to wait till</blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
the backend is idle or disturb ongoing recordings.<br></blockquote><div><br></div><div>I run a frontend on my server... never once had to reboot the server due to a frontend related issue. Even if I did, it's only a secondary frontend, not my primary viewing system... if the frontend broke and needed a reboot, I could wait until a safe time. And seriously... this is TV. If I had to reboot during a recording I would miss what, 1 minute or so of everything that was recording at the time... hardly a tragic loss.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Also in essence the demands for both are different. A frontend needs<br>
to be quiet and have powerful enough graphics and sound and it is nice<br>
if it looks nice. A backend just needs enough power to do what it must<br>
and before most it needs to be stable. You could even leave out the<br>
graphics and the sound.<br></blockquote><div><br></div><div>None of this makes a bit of difference when the OP clearly stated that his backend is sitting right next to his painfully slow ION frontend. The combined noise of two machines will be louder than one... the ugly backend appearance is not somehow improved by setting a pretty frontend computer next to it. </div><div><br></div><div>Essentially your arguing that he would be better keeping the frontend on hardware that he said he is no longer happy with rather than utilizing the overpowered backend sitting right next to it.</div><div><br></div><div>In an ideal world we would all have our backends hidden away in a closet somewhere... but in the real world we sometimes have to put them wherever we can... and if I have to have my backend anywhere it would be convenient to also have a frontend... then it would be just plain stupid not to have it do double duty.</div><div><br></div><div>Believe it or not, most mythtv installations are combined Backend/Frontend, or at least they started that way.</div></div></div></div>