Improve the performance of pre-allocation under SSD

[StarrySky RGZ]

I have a Windows Storage Space Tiered Storage.
Pre-allocation will broken write-back cache, and it look's like design for HDD.
Low-cost SSDs are generally designed "SLC Mode Cache", Pre-allocation will fill it up and cause worse performance.

Anyway, reserving space and reducing writes is feasible. "SetFileValidData()" can very quickly create a big file and without fill zero in the file.

This is very suitable for SSD, SSD will not be affected by fragmentation.

Details:
https://stackoverflow.com/questions/12228042/what-does-setfilevaliddata-doing-what-is-the-difference-with-setendoffile

[EmotionallyBroken]

I thought the whole point of SSDs was that fragmentation wasnt relevant as data can be scanned from anywhere immediately with no moving parts?
EDIT: Or is that still slightly a reduction in performance due to the nature in the reading system?

[StarrySky RGZ]

Messaggio originale di 250RoundMags:

I thought the whole point of SSDs was that fragmentation wasnt relevant as data can be scanned from anywhere immediately with no moving parts?
EDIT: Or is that still slightly a reduction in performance due to the nature in the reading system?

The data stored in the SSD is discretely distributed and fragmented.
And it’s all opaque
Therefore, all defragmentation operations are futile and will wear out SSDs unnecessarily

For file systems, the storage address is contiguous and the conversion is done by the FTL of the SSD. (Opaque operation, no one knows where the data on the SSD)

[Iceira]

Messaggio originale di StarrySky RGZ:

Messaggio originale di 250RoundMags:

I thought the whole point of SSDs was that fragmentation wasnt relevant as data can be scanned from anywhere immediately with no moving parts?
EDIT: Or is that still slightly a reduction in performance due to the nature in the reading system?

The data stored in the SSD is discretely distributed and fragmented.
And it’s all opaque
Therefore, all defragmentation operations are futile and will wear out SSDs unnecessarily

For file systems, the storage address is contiguous and the conversion is done by the FTL of the SSD. (Opaque operation, no one knows where the data on the SSD)

yeap all that is true but there is one thing many forget that is filled space that is made correctly
so once a year do a defragmeting only for max usage for free space, but its not for things go much faster only about used space issue. that is the only rule left in SSD

but whats the point anyway then windows OS screw SSD up anyway, for access and dump data anyway
superfetch and other frequent acces of preaccess things then its not needed anymore. so disk is dead anyway within 5years, so many get SSD crash any noone know why.

ohh and dont forget that swapfile even that will resize all the time and change content on a SSD. ( so how cares about framentations anyway , unless you have removed from sytem to have it but that also lead to more bottleneck so, and as gamer and i just buy new SDD then its burn out. so fragmentions is not a big issue if all other frequent access system files keep write at disk anyway )


i think i had to delete the game and reinstall it to fix that Pre-allocation that game do. not sure what cause it.

go see taskbar sort after disk and look at that tiny write to disk all the time. and then ask yourself who care about Diskdefragmention anyway, i will say even if you did it once a week on SSD i doubt it can be a issue then you look at all that mini tiny write to disk all OS services do anyway. disk will die its only matter when.

all that mini acces sould be in ram not SSD disk , MS and all our service app should maybe have educations money back then in my case have 16gb ram installed why use my disk for 0.1 write at disk all the time. ( and as long that is not solve why bother with SSD disk you could fragment it every day and yes it will reduce lifespan but so will all the app that keep access it.

[A.M]

wow

[Iceira]

ohh sorry, i dont have to tell you anything go see disk writes in task manager and then you might see how poor things work see from a SSD disk point of view. ( it do look like more how fast can we burn a disk up then try keep it alive dont forget its a system disk all thing will be change alot and that is the problem it should be in ram only no temp data allowed on SSD its either write or read, that will expand lifespand no temp at all swapfile in ram and so on. and i can see this will end the debat, because it has never been there where it should have been in a long time, you actual need a true ram disk or have way more ram blocks system need to dump data. )

[Satoru]

My presllocarion on my SSD and normal drives takes a normal amount of time

You’re likely CPU bound in some way or your anti virus is killing it

[StarrySky RGZ]

Messaggio originale di Iceira:

yeap all that is true but there is one thing many forget that is filled space that is made correctly
so once a year do a defragmeting only for max usage for free space, but its not for things go much faster only about used space issue. that is the only rule left in SSD

 

If you want to restore performance, you can use Secure Erase (SE) - but this is not necessary for a well-designed SSD

Defragmentation is not necessary, only SSD-level GC (Garbage Collector) can improve performance

For the operating system, only TRIM is needed to make the SSD aware of the LBA actually used.
This allows SSDs to maximize free space and reduce write amplification

The cause of most SSD failures is not too much writes.
FTL damage caused by unexpected power failure is a common cause of failure

If you really care about SSD life, then Steam pre-allocation is worth your attention.
It caused 2x data to be written

[Iceira]

yeah we all know that , if you have follow the change over time, and yes alot other things happend by unexpected power failure or other whatever melt down, but it still get better and apps have learn ohh you have a SSD disk, but it still same thingy
things that keep write to disk is bad = and as long that aient fixed. imo that itself will not prolong lifespan of disk. and it is actual a MS problem for not dump this in ram. all apps see write to disk with change rather then dump it at ramscoope as we call it in the old days.

but if you remember old days defrag trim and other things was added later. most did not even see a SSD disk so go figure, and that tells alot about devs they dont follow what tech they are have apps with. they did a catch up , and complain from users. but lets not debat that.
fair enough something is new, but there it is. gl with it