<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><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<br>
> >>> > it... just combine them.<br>
> >>> ><br>
> >>> > While his machine should be powerful enough to do both I don't like<br>
> >>> > them to be in the same machine.<br>
> >>><br>
> >>><br>
> >>> I respect your opinion, and while we all wish we had unlimited resources<br>
> >>> where we could dedicate a computer to single purpose, you must admit it is<br>
> >>> a bit wasteful.<br>
> >><br>
> >> If you aren't worrying about supporting any backend features, you can<br>
> >> easily get suitable low profile machines with a proper graphics card for<br>
> >> cheap.<br>
> >><br>
> >> If you aren't worrying about the machine being small or quiet or even<br>
> >> having a decent video card, you can get some really good deals on hardware.<br>
> >><br>
> >> Combining the two complicates both and can escalate prices dramatically.<br>
><br>
> > I'm having a very hard time imagining a case where a combined FE/BE<br>
> > system is more expensive/complicated than a dedicated FE and a<br>
> > dedicated BE purchased separately, even if the cost of the combined<br>
> > FE/BE machine is higher than either the FE or BE alone.<br>
><br>
> > It's hard to put together a decent FE system for under $200, where<br>
> > it's easy to upgrade a BE to a quiet FE/BE for less than that. I have<br>
> > a Corsair water cooler block on mine (~$50) and I replaced the single<br>
> > fan it came with with two new ones ($9 each) in a low speed push-pull<br>
> > configuration. The machine is quiet enough for the living room<br>
> > without being noticeable, despite the 8-core cpu in the box.<br>
<br>
</div></div> Acceptable is a matter of opinion. This includes size and appearance<br>
and noise levels. A system that seems quiet enough may be intolerable to the<br>
next person. A giant ugly PC in the middle of the living room may simply be<br>
not an option. As soon as you start dealing with smaller form factors, you<br>
lose a lot of flexibility and prices tend to increase dramatically.<br></blockquote><div><br></div><div>The OP never said that this would be in his livingroom... only that he currently has an underpowered frontend "in the same place" as his backend. And wondered if it would be a good idea to combine the two. Since he is currently running separate backend and frontends and hasn't moved his server somewhere else, we can assume he is content with having his backend remain in its current location.</div><div><br></div><div>The only question we need to answer for him is if it makes sense to run a combined system, or continue to use two separate systems right next to each other. Lets stop discussing noise and appearance... they aren't relevant to the discussion. If he intends to keep the back end where it is, it simply isn't logical to put a frontend right next to it... what is logical is to run a combined system at that location. Then he can use his ion system at another location if he chooses.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> 2 simple boxes versus a more complex one is not wasteful. Each can be<br>
optimized for their own requirements. They can be isolated from each other.<br>
One can be completely disconnected from power without impacting the other.</blockquote><div><br></div><div>Two separate boxes are definitely more wasteful no matter how you measure it. Take any suitable backend system and drop in a GPU (inot even necessary with modern cpu/gpu combos) and you have a suitable combined system... how can you think it possible to take that same GPU and wrap a whole second computer around it and come out ahead.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The fact that you don't need to cram everything into a single box is<br>
one of the key advantages of MythTV.</blockquote><div><br></div><div>Being able to have remote frontends is definitely one of the selling features.... but no one has ever suggested that it was the intent of the developers that people do not run both on the same system. In fact, it was their intent that people have the ability to do just that.</div><div><br></div><div>You seem locked into the idea that a backend system has to be big and ugly. Most HTPC's and DVR's are standalone systems, as mythtv is one of the few that allows you to break things up.</div><div><br></div><div>I have built several mythtv combined systems for others that are nothing but a MiniITX case with a single spinning disk and a HDHR tuner somewhere on the network. These systems are quiet, fast, and efficient. </div><div><br></div><div>Just because mythtv allows you to build a giant, noisy, power hungry backend server and locate it on top of your toilet tank... doesn't mean that it's the 'right' way... it all depends upon the goal your trying to reach.</div><div><br></div><div>With today's 4TB harddrives... even without transcoding you could store about 700 hours of MPEG2 video on a single spindle. If the OP is somewhere that gets h264 video, it would be over 1400 hours; enough to make most people happy. So most people don't need a big noisy system... just a little box with a decent CPU/GPU, a fair amount of ram, and a nice big harddrive.</div><div><br></div></div></div></div>