On 11/17/2010 1:27 PM, Frank wrote:
> On Wed, 17 Nov 2010 15:22:53 -0000, John McGaw <(E-Mail Removed)> wrote:
>
>> On 11/17/2010 9:27 AM, Frank wrote:
>>> Newbie starting a new build with a SSD 64GB drive which I intend to use as
>>> the boot and a separate 1TB drive for programs/storage.
>>>
>>> Question: should I only put the Win-7/64 files on it and/or other files
>>> to utilize the speed of the drive?
>>> Thanks.
>>
>> I did an 80gB Intel SSD and a 2tB data drive with 3 partitions on the
>> same OS but I guess the principle is the same. I finally decided that all
>> of the OS files along with the most-frequently-used programs and
>> utilities would go on the SSD and everything else would go on the data
>> drive. Having the programs I load most would allow me to take advantage
>> of the speed of the drive -- a program which gets run once a month, even
>> if it took a relatively long time to load from the rotating drive, would
>> cost me little. Smaller programs loaded frequently would add up to a lot
>> more time coming from the slower drive. I just checked and the SSD shows
>> 43.5gB free out of 72.2gB and I try to make sure that the SSD never gets
>> more than 1/2 to 2/3 full out of concern for NAND wear and sparing (this
>> may just be paranoia on my part).
>
> Never thought about multi files v large files. Being lazy will probably just
> load the SSD with most used. However, you do have me on NAND?
> Thanks for the tips.
> Frank
NAND is the type of flash memory used for data storage inside the SSD. The
memory has a definite number of cycles it can run through and part of the
SSD controller's job is to keep track of used/unused and when a given area
of memory "wears out" the controller moves the data elsewhere. I'd prefer
to be cautious and leave the SSD sparsely populated but, like I wrote, this
is probably just my own paranoia about component failures.
|