Partitioning between SDD and HDD

[jdow]

In the past in theme park ride applications we've had audio on SSDs.
The same audio gets read every few minutes virtually every day of the
year. Eventually the audio files developed bad spots. We started
recommending they record a full day's worth of the audio and play
sequentially to the end of the recording before starting over. That
solved the bad spots caused by reads.

This was a few years ago. Times might have changed. I am still leery
of SSDs, though.

{^_^}

On 2012/12/26 03:21, J.Witvliet at mindef.nl wrote:
> Just my 2 cents, though personal experience.
>
> 18 months ago i replaced on a machine the traditional hdd with a sdd. And
> indeed, it started and worked like greased lightning.
> However, i installed it like i used to do, with swap....
> One year (and many patches) later, i got that many bad blocks that the sdd was
> completely useless.
>
> So sdd has it merrits but:
> A) no swap on sdd, so either enough mem, or swap on traditional hddm
> B) keep things like /var so on hdd
> C) if you _realy_ enough mem, put /var and /tmp on tmpfs (eg, in mem)
>
> Hans
>
>
> *Van*: Eddie G. O'Connor Jr. [mailto:eoconnor25 at gmail.com]
> *Verzonden*: Friday, December 21, 2012 08:23 PM W. Europe Standard Time
> *Aan*: Community support for Fedora users <users at lists.fedoraproject.org>
> *Onderwerp*: Re: Partitioning between SDD and HDD
>
> On 12/21/2012 11:51 AM, Alan Evans wrote:
>> On Fri, Dec 21, 2012 at 6:35 AM, Eddie G. O'Connor Jr. wrote:
>>
>>     You mean that all this hype over SSD's and they're LIMITED? I thought they
>>     were supposed to be BETTER than the spinning drives of today? Exaclty how
>>     are they better if they come "out-of-the-box" with limitations? Just
>>     curious...
>>
>>
>> It's well known that flash devices have a limited number of writes. This
>> number is pretty high, though. And with caching and load-balancing built into
>> the drive's firmware, it is typically not a major concern.
>>
>> However, although SSD devices have lightning-fast read performance, writing to
>> them is considerably slower. Think of the difference between reading a big
>> file from a flash thumb drive versus writing a big file. That doesn't mean
>> that you should never write to them, but if the intended use involves writing
>> very frequently (like /var or /tmp) then it might not be a good fit.
>>
>> Also, SSD is much more expensive, byte-for-byte, than a hard drive. If you
>> want a lot storage (my /home partition is well over a terabyte) then SSD is
>> pretty cost prohibitive.
>>
>> On the other hand, my system drive is SSD and, because of the fast read
>> performance, my computer boots, after the BIOS screen, in four seconds. From
>> the login screen to my desktop is another 2-3 seconds. Starting even very
>> large applications is pretty snappy.
>>
>>
> WOW!.....talk about speeding up. Well I have a Gateway laptop so there's not
> physical way I could do 2 different types of drives, but I also have a CentOS
> desktop, maybe I can do it there, is SSD something that an old "Pentium 4" PC
> could use? I think I'll look into this...do some Googling! Thanks for the info!
>
>
> EGO II
> --------------------------------------------------------------------------------
> Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de
> geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u
> verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat
> aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband
> houdt met risico's verbonden aan het elektronisch verzenden van berichten.
>
> This message may contain information that is not intended for you. If you are
> not the addressee or if this message was sent to you by mistake, you are
> requested to inform the sender and delete the message. The State accepts no
> liability for damage of any kind resulting from the risks inherent in the
> electronic transmission of messages.
>
>