RAPID mode gives fantastically high results for benchmarks, where the test
software just basically writes out data that it rereads later on.
If the RAM cache is large enough, the test will only measure the RAM speed,
rather than the disk speed.
For example, the Samsung 850 EVO 2TB Review article from August 2015 gives
test results from three well-known products :
ATTO
Astonishing. Previous speeds were 559MB/s Read and 537MB/s Write, and
with RAPID Mode enabled we’re seeing a nearly unbelievable difference
at 3555MB/s Read and 3723MB/s Write!
Crystal Disk Mark
More of the same here, as results here jump to an absurdly fast
6321MB/s Read and 4239MB/s Write (up from 541 / 522 stock) in the
Sequential test.
AS SSD Benchmark
Another massive jump, with Sequential Read and at 3602 MB/s and 2380
MB/s, respectively (up from 520MB/s Read and 500MB/s Write in stock
mode. And look at the overall score increase, from 1091 jumping up to
36568. Wow.
However, in everyday life we don't always re-read the data we have just written,
so the results are vastly different.
I have found several user testimonies :
Windows 10 Forums - Samsung Magician, July 2015
Only in the synthetic tests. There is some improvement in copying
large files between two SSD drives. I used to do very high cue depths
work at one time and enabling rapid definitely helped. Under normal
use and gameplay, cannot see any difference. I can tell you this, it
doesn't hurt. Just one person's opinion.
It definitely does not help boot times. In fact the rapid service only
loads during the boot process and at best, would create a minuscule
delay in the boot process.
Direct X & Samsung Magician, March 2015
For benchmarking it appears good, but actually in real-world
performance, just slows down your boot, adds another background
process, and doesn't speed up game performance or anything majorly
useful. It's a have, and personally I see little to no point in using
it, other than to give a faked illusion of more performance (which
happens to be more unstable as well on quite a few system, which is
why they leave it disabled as default).
And the next remark :
I had issues with the Samsung magician "Rapid Mode" on, i was not able
to play any of the counter strike games. They started and after a few
seconds they would froze. After turning off the rapid mode, all was
good.
Conclusion
Under normal everyday use, allocating up to 25% of your RAM to RAPID
takes this memory away from Windows (and the same for Linux).
Windows & Linux incorporate very good memory caching which I believe will
better (and safer) handle everyday use.
Especially as they use this RAM for more
purposes than just as a disk buffer (programs, memory data etc.).
With RAPID, one also has higher chances of losing data when power is lost
or when the computer crashes before a write has been completed and sent to the SSD, as RAM contents are then lost.
I would therefore not counsel using RAPID for normal computer usage.
It's suggested here that running WinSAT can reset from SSD to HD.
I'm not sure what he means by 'Full Assessment'. The available parameters are on Technet.
You can try winsat formal
If that doesn't work, try the various winsat disk options.
The maintenance task is supposed to run winsat weekly to detect hardware changes.
Best Answer
The short answer is no, you don't have to do anything special.
When you delete a file, you're basically telling the filesystem that the storage area reserved for the file on disk is now free for reuse. This is true for both an SSD, and a regular disk. The file data isn't really completely gone until something else uses some of that freed up space and overwrites it.
On a regular drive, there is essentially no limit to the number of times you can reuse a block of storage. Storage blocks on current SSDs will physically fail after a number of writes that is small enough to matter. SSDs avoid failing by doing something called wear leveling. This means the drive will try to actively distribute use over all blocks as evenly as possible.
So, while a file isn't really gone until the storage blocks get rewritten, the blocks tend to get reused/rewritten more rapidly on a regular disk than on an SSD. If you're concerned about data security, writing over a file then deleting it gives you some assurance on a regular drive (although there are more complications than you might imagine). This is much less the case with an SSD. Writing over the file will most likely mark the old blocks as free and write to new ones.