I don't see why you are so confident that the SSD wear leveling
algorithm would treat (pagefile.sys) like any ordinary file.
Obviously it doesn't, considering a reboot is required whenever
that file is changed.
Oh my god, did you just say that?!? You're obviously one of those who
only has enough information to hang yourself by. Windows, the operating
system, is the one that requires a reboot, Windows is the one that
treats pagefile.sys specially! It's not the SSD that cares, it's Windows!
The SSD itself has a layer of abstraction below the interface that
Windows or any other operating system isn't even aware of. This is
actually no different than the case with hard disks, because they too
used to have layers of abstraction below the OS which they used to
replace bad sectors with good ones, etc. But the SSD takes this several
steps further.
In the meantime, you've used nothing but bellicosity and ill-manners to
insult every person in this thread that tried to help you. All to cover
up your obvious lack of knowledge. What was the purpose of that?
As far as I know, the operating system addresses the swap file
differently than other files. That's why it is unmovable on the
drive. Seems to me it would be addressing the actual locations on
the drive, instead of working its way through drive software.
Unless you're an engineer, I'm very sure you don't know better.
Yes, "as far as you know", which you've demonstrated is not much. It's
Windows that makes it unmoveable, so any utility, like a defragger will
not be allowed to touch it, because Windows will prevent it. However,
Windows has no control over its location below the SATA interface level.
The SSD move it all over the place as it likes, whenever it is
necessary, but it doesn't tell Windows about any of it. That's because
Windows doesn't need to know, and it doesn't care how it's organized at
the physical level. At the logical level, Windows does care, but Windows
deals with the logical level, the SSD deals with it at the physical level.
Yousuf Khan