Best ssd for compressed files

Most media is already compressed, so there isn't much savings available there. However, compressible files like server logs and Excel data will yield a lot more space. There's one more point to consider, though. With information being compressed on the fly, you're consuming more of an SSD's available write cycles than if you were writing the files uncompressed.

This could have negative implications on the drive's endurance. Although we're not necessarily concerned about larger SSDs, models with less capacity inherently have lower endurance ratings. Thus, NTFS compression could conceivably affect their useful lives more significantly. Topics Samsung. See all comments I've been wondering about this very topic for a while now.

However, in the conclusion, it is stated that compression ends up writing more vs. Shouldn't the opposite be true? When writing to the file system, if a file is compressible it should take up less space and therefore conserve more PEs though actually compressing the files for the first time should result in more writes. Why does on-the-fly compression result in more writes even though the amount to be written is smaller?

An interesting article, but seems a bit contradictory. Kind of like buying a Ferrari and then worrying about the gas mileage. Leave some free space To extend the lifespan, most SSDs use wear-balanced algorithm. Way 3. Way 4. Disable Hibernate Hibernate mode is set up by default to allow the hard drive disk to load the programs faster instead of booting the system, but it becomes unnecessary for SSD system drive as it takes seconds to boot system from SSD.

To free up more space by disabling Hibernate: Type the following command: powercfg -h off in an elevated command prompt and press Enter Way 5.

Disable Disk Indexing Indexing is a good feature designed to provide quick access to files or folders on a hard drive, but it becomes pointless on an SSD.

To optimize SSD on windows 10 by disabling disk indexing: 1. Right-clicking on the specific drive in This Computer, and selecting Properties. Way 6. Disable Superfetch To optimize Windows 10 for use with an SSD, you can disable Superfetch, which waste a large amount of time opening and accessing files multiple times. Way 7. Adjust page files The Paging file has a controversial effect depending on how much RAM you have in your computer. To adjust page file: 1.

Right-click on This Computer, and select Properties. Flexion [H]ard Gawd. Joined Jul 20, Messages 1, So I went ahead and compressed my Program files folders both X86 and X64 , and I'm happy to report that in the very least I don't "feel" there's a performance penalty.

The thinking was that modern CPUs are fast enough to handle all of the overhead needed to decompress the compressed folders, and overall less data is actually being read and written to by the drive. Also, the access time is so small, that all of the seeks that used to slow down compressed hard disks are a non issue. It was hard to quantify, and AS SSD benchmark strangely reported lower numbers, even though it was using clean free space for the benchmarking.

Otherwise, games load up just the same as they would normally. Any opinions? Joined Feb 16, Messages 2, So i don't think it will particularly help with speeds; it may yield more space to store stuff on SSDs however. Click to expand Bahamut n00b. Joined Apr 27, Messages 0. The theory is simple, I'll try to make it brief which means I'll explain it with way too many words, as usual Say you have a MB file you need to load into an app, the app itself is already open and waiting.

Say the MB file is uncompressed presently, but the file is made up of highly compressible, and we'll use the oh-so-common ratio of meaning if you did use NTFS compression, you'd end up with a compressed version of the file on the platters that's 50MB in size. You'd verify that by right-clicking on the file icon or name and choosing Properties where Explorer would tell you "Size" which is the native uncompressed actual file size, and "Size on disk" which would tell you the size of the file as it exists in the now compressed form, rounded up to the nearest 4KB boundary given the 4KB cluster size of NTFS unless you altered that, bad idea.

Ok, now the math: Let's say it takes 1 second, precisely 1 second to load the original uncompressed MB file into the app, 1 second exactly.

Logic would dictate that to load a file exactly half that size should take exactly half the time, and let's say on your example machine it does. If you were loading a 50MB uncompressed file it would load in. Now the fun part: On today's modern computers doing mathematical operations is a cakewalk.

NTFS uses a form of compression known as LZ77 which is incredibly efficient and very fast in operation. So fast, in fact, that this is where our potential speed benefits come from. If that happens on every single read operation that could translate into even greater overall performance, especially on very compressible data like run-time libraries, executables, the OS and the applications themselves, even a lot of different types of data like documents, etc.

Now, for all those hardcore people wanting the absolute maximum levels of performance, compressing the file system NTFS on an SSD can have potentially massive payoffs in terms of performance. Now translate such a benefit across every file on your hard drive or SSD that's compressible, even to small degrees and you get a boost in read performance.

With hard drives and SSDs you're already taking a tiny penalty on write performance as it is more often than not, so, adding a tiny bit more of a hit to create the compressed version of a file that first and probably only time unless the file changes frequently , and with all forms of data storage getting faster all the time on top of the CPUs and RAM speeding up as well , there are no negatives to this simple change of adding NTFS compression to your SSD-powered box.

Applies to other OSes with file system level compression as well, of course Most people that use multiple drives or partitions nowadays do it for better organization, but this type of compression-based "boost" is only going to be effective at loading small compressible files like those that make up the OS itself on the drive, and the applications that people typically use the actual application code.

If you have tons of mp3 files or some other format of music content , video files, DVD rips, Blu-ray rips, etc - anything that is NOT highly compressible data, and takes up huge amounts of drive space, this type of file system compression is not going to suddenly double things across the board; in fact it might actually hurt performance.

People get SSDs to make their OS load and function faster and their applications follow the same pattern; don't waste a lot of SSD space on big storage items, it's too inefficient unless you just can't help it. NTFS compression can give you an even better level of performance when it's properly implemented as explained above. It's not doubling the speed of your storage but it is making things load a lot more efficiently from that time perspective which translates into that effective difference in performance.

That should spell it out succinctly. If for some reason you're not happy with the increased performance on most every single read request your system makes off a compressed file system , you can reverse the entire setup with a few mouse clicks, piece of cake. Cantonious Gawd. Joined Jun 22, Messages Bahamut said:. Must be some insanely compressible content in those folders Well you do have a rather monstrous machine by pre-Core generation standards so Joined Dec 12, Messages 1,