While there are reports of SSD limits to the life of the drives regarding writes, I personally have yet to experience a single hiccup with an SSD used for DJ applications. I play all video at events but do very little hardcore editing. I do a lot of DVD ripping to .mp4, but again, little editing post rip. I've experienced more disc failures in the standard drive 5400 rpm class than in any other speeds, regardless of brands.
What I am trying to discern is the properly sized swap file when using all SSD and having maxed out RAM. There are all kinds of opinions in every direction imaginable. So far, in experimentation of my usage patterns, having no swap file has given me the best overall performance while allowing Windows to manage it had created one annoying issue wherein the drive will stall and freeze for about 60 seconds once or twice a day and mostly after several hours of at idle.
Cap - just food for thought:
No matter how much RAM you have, you want the system to be able to use it efficiently. Not having a page file at all forces the operating system to use RAM inefficiently for two reasons:
First, it cannot make pages discardable, even if they have not been accessed or modified in a very long time, which forces the disk cache to be smaller.
Second, it has to reserve physical RAM to back allocations that are very unlikely to ever require it (for example, a private, modifiable file mapping), leading to a case where you can have plenty of free physical RAM and yet allocations are refused to avoid over-committing.
Consider, for example, if a program makes a writable, private memory mapping of a 4 GB file. The operating system has to reserve 4 GB of RAM for this mapping because the program could conceivably modify every byte and there is no place but RAM to store it. So from the start, 4 GB of RAM is basically wasted (it can be used to cache clean disk pages, but that is about it).
You need to have a page file if you want to get the most out of your RAM, even if it is never used. It acts as an insurance policy that allows the operating system to actually use the RAM it has, rather than having to reserve it for possibilities that are extraordinarily unlikely.
The people who designed your operating system’s behavior are not fools. Having a page file gives the operating system more choices, and it will not make bad ones.
There is no point in trying to put a page file in RAM. And if you have lots of RAM, the page file is very unlikely to be used (it just needs to be there), so it does not particularly matter how fast the device it is on is.