View Single Post
  #5  
Old October 12th 18, 01:13 AM posted to alt.comp.hardware.pc-homebuilt
VanguardLH[_2_]
external usenet poster
 
Posts: 1,453
Default SSD and sleep mode?

VanguardLH wrote:

Mike wrote:

Got any better free ideas on what to configure for optimum SSD life beyond
what's shown in SSD Fresh?


You still need a paging file, even if only a small one. If you have an
internal HDD, split the pagefile across the SSD and HDD with the
majority on the HDD.


Also, you will hear lots of arguments against defragging your SSD.
However, defrag.exe in Windows will recognize an SSD but still optimize
it. There's something about file systems that users never consider as a
consequence of fragmentation: an increase in the metadata stored in the
file system as fragmentation increases for a file. Eventually a file
can become so fragmented that the file system can no longer keep track
of its metadata which results in errors when you try to write or extend
a file.

http://www.ntfs.com/ntfs-system-files.htm
https://www.hanselman.com/blog/TheRe...YourSS D.aspx

Unless someone chimes in declaring there is a version of NTFS that
accomodates wear-levelling in SSDs where every write is to a different
block of memory and somehow can either track more metadata per
fragmented file or eliminate fragmentation without incurring whole-file
writes versus delta writes then fragmentions of SSDs with NTFS can
result in too much to track per file. However, I have not found what is
NTFS' limit on metadata per file or performance impact on SSDs on
writing more metadata for a highly fragmented file. In any case,
metadata occupies drive space (1024 bytes in the MFT per fragment).

Only if Analyze to show the whole fragmentation value for a drive is
zero does it mean no file is fragmented. If anything other than zero,
it doesn't tell you which files have the highest number of fragments.
If analyze says fragmentation is other than zero, you really don't know
if any file has too many fragments by itself. Defrag will retrim an SSD
and that's a good thing. For a server or heavily used workstation,
trims can accrue and get dumped; however, there is so much idle time on
an end-user PC that a queued trim will get executed (by Windows or by
garbage-collection logic in the SSD).

If you check, and what I found in Windows 7 with an SSD, is that Windows
still runs its defag.exe against ALL drives, including SSDs. You'll
find an event in Task Scheduler for "defrag.exe /c". Alternatively, you
can run Disk Defragmenter (GUI version) and click on Configure Schedule
to either disable all scheduled defrag events or modifying on which
drives it gets exercised. It's up to you whether or not to leave
enabled or disabled the optimize on your SSD to reduce the number of
writes to it. Data integrity is more important to me than endurance of
the storage media hence the need for backups.