<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jul 23, 2014 at 2:49 PM, jacek burghardt <span dir="ltr"><<a href="mailto:jaceksburghardt@gmail.com" target="_blank">jaceksburghardt@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 dir="ltr">Well do you guys think that using ssd for buffer will imrove mythtv ?</div></blockquote><div><br></div>
<div>
Define improve.</div><div><br></div><div>Unlike others, I like the idea of using an SSD as a recording drive... because of the lack of access times I could easily sustain all of my recordings and playback on a single drive... i currently use 3 spinning recording disks. Using a user job I could then move them a week or so later to spinning media. This solution would allow my spinning media to sleep except when actually moving the recordings over, or watching an episode that recorded over a week prior, and it would let me reduce the spinning media to a single large drive. Note, I tried recording 5 HD streams to a single spinning disk, and while it seemed to work, I could hear the drive thrashing. Spreading the recordings over 3 smaller drives made a huge difference, especially because I have peaked at 8 HD recordings at once.</div>
<div><br></div><div>For the database, you can see a substantial improvement unless your mysql configuration is heavily optimized to eliminate disk reads.</div><div><br></div><div>For the OS, it doesn't really matter... once the system is up and myth is running, there isnt much going on.</div>
<div><br></div><div>For mythfrontend, you might find it a bit snappier loading artwork, channel icons, etc... probably not much though considering I don't have any complaints running the frontend on a diskless/iscsi system.</div>
</div></div></div>