Should the pagefile be placed on SSDs?

Thundordan

n00b
Joined
Feb 12, 2010
Messages
29
Hello everybody,

Now before you answer, read http://blogs.msdn.com/b/e7/archive/2009/05/05/support-and-q-a-for-solid-state-drives-and.aspx -- Ctrl+F "Should the pagefile be placed on SSDs?".

I am in the bad habit of keeping 100+ tabs open in Chrome at a time, (aside from other things), which chews up most part of my 4GB DDR3's. A few times I could actually noticeably benefit from a USB readyboost because of this.
Long story short, my WDC7200RPM HDD works extra hard with the paging and temp files, bottlenecking me horribly..:(

Now I could just manage my Chrome sessions, but the point is, it would be just brilliant if I could store my page file, caches, Photoshop temp folders etc. on a SSD.

Since I can't afford a large SSD and my Program Files alone take up 39GB (no games whatsoever), I would like to buy say, a 8GB fast SSD and use it as a paging/temp_file drive.. (later on I'd like to buy a NAND http://www.geek.com/articles/chips/...eap-ssd-with-25nm-process-technology-2010022/ if they actually come cheap enough).

I've read things such as "BTW placing the page file on the OS drive will provide the optimum results!! and using a ram drive (there are some good guides here) for any temp files will allow you to use the SSD's for their intended purpose!!" but the link I posted seems to contradict them..

:rolleyes: What say you? Surely it would be faster than holding a 6GB page file on C:\ which grinds almost to a halt whenever I search for a file, unrar something and open a new tab..

Also, how can you tell Windows7x64 to point all it's caches and temps to a separate drive/partition?
 
The 8GB SSDs on newegg are ~$100 each, you can save money AND have a more guaranteed performance gain by getting more RAM. Assuming you currently have a 4 RAM slot mobo and 2x2GB DDR3, buy 2x2GB more. I similarly have issues with 4GB, its too little, I hate it. 8GB all the way, man.
 
I can open 200+ tabs in Firefox, seriously (I did it a few times for testing) by basically having Firefox open all my bookmarks in tabs in a single operation. Took a few minutes for everything to fully load, but on a 4GB DDR3 laptop Firefox still didn't crack 1GB of RAM usage and on top of that I run Firefox from a RAMdisk and cache all the data in RAM too...

If your machine is chuggin' along with 100+ tabs in Chrome, maybe you should consider a new browser. :D

You should use a RAMdisk to re-assign all the cached data from the browser (whichever one you choose) and send all that data to the RAMdisk which is massively efficient over using the hard drive for such things.

I am not suggesting or telling you to put a page file on a RAMdisk, however - that's possible with some RAMdisk apps but it's not what I'm suggesting. The suggestion is get a RAMdisk and use it for all temp variables, browser caches, etc etc. DataRam makes a free one that works with Windows just fine, SuperSpeed RamDisk Plus is a commercial product that works great as well - that one supports a page file placed on a RAMdisk but again that's not my suggestion.

You'll notice two things primarily by doing so:

1) Your web browsing will be insanely fast if you set this up correctly, even faster than any SSD drive out there today and for years to come probably since RAM is still way way faster than SSD's are or will be capable of anytime soon, and...

2) You can even run the browser itself from RAM and get even better performance overall (all the modern browsers today offer portable versions (except IE of course) which in many respects are superior to a fully installed one). You can get a portable version of Chrome, Firefox, Opera, SRWare Iron, etc and run them directly from RAM, with all the data they create in RAM, with all the data they cache in RAM, and things then take on an entirely new level of performance.

If you open the System Properties and look at the Advanced tab, there's a button near the bottom for Environment Variables which you use to reassign to new locations (the TEMP and TMP ones are all you need to muck with). Pointing those to a RAMdisk of about 512MB to 1GB in size will have a dramatic effect on system performance overall, not just for web browsers. Then point the browser caches to the RAMdisk as well and it just gets better and better.

Best advice? Stop leaving 100+ tabs open, simple. :D Close shit... I mean I consider myself excessive at times with 40+ tabs open but, I don't leave 'em open, I get what I need from them when I do get that many and I close 'em... 100+ tabs... geez man, you need some addon that tells you "Hey, dumbass, you're leaving tabs open again, start closing 'em... or I will..." or something like it. :D

I've got 4GB of RAM in this laptop and a 1GB static page file, and I've pushed this thing fairly hard at times - and I use a 1GB RAMdisk 24/7 as well as I just described above, and I run about 14 apps in portable form from that RAMdisk as well as it being used for all of my temp files/variables/browser caches, etc... and I've never had Windows 7 complain one time.

Oh, and I'm using Windows 7 Pro x86... the 32 bit version, and I still make use of all the 4GB of RAM because of that RAMdisk as well (SuperSpeed's RamDisk Plus). Not a byte of it gets wasted... :p
 
Chrome doesn't even have a drop down list of open tabs like Firefox, how are you managing your 100+ tabs?

Bahamut, any browser will use minuscule amounts of RAM when you first start, its the act of leaving the tabs open 24/7 + memory leaks that makes it use crazy amounts of RAM. For me, leaving my facebook tab open for a week can make that process (in Chrome) use up 1GB RAM all by itself. Quick solution is to open Chrome's task manager, sort by RAM usage, and close the large RAM users. You can do undo close tab (Ctrl + Shift + T) after each close to quickly bring them back up with minimal RAM usage once again right after.
I'm betting Thundordan leaves Chrome open.

Ultimately, you should just get more RAM and never even need to think about this stuff.
 
I don't have memory leaks with Firefox, I never have had leaks with Firefox. Personally I think that's a bullshit myth with people doing crap on their machines that fucks things up - I can't say what it is but, I've had times where the same instance of Firefox 3.x has been running for days upon days at a time and if I close every tab I go right back down to ~125MB of RAM usage (and remember as I just said, everything Firefox does is cached in RAM so a big chunk of the ~125MB is actually cached code - I have Firefox set for a 96MB RAM cache, not hard disk based).

I see you point out you're using Chrome too and excessive RAM usage... you folks really should pay attention to that fact because for all the so-called complaints about Firefox and RAM usage, I see 20x more complaints for excessive RAM usage in Chrome nowadays on most of the forums I frequent.

I honestly do not have the problems other people do with Firefox, and I can't stand Chrome at all and only use it for simplistic testing from time to time.

My Firefox has been portable for nearly two years now, started with Firefox 3 and has been "upgraded" in place with each new release that's appeared to the most current which is 3.6.8 - it's been in the same folder all this time, and I've got 23 addons installed and I use them with alarming frequency daily. About 55MB in size at the moment because nothing is cached in the folder hence it remains small and I regularly clear out the sqlite "gunk" databases too.

I really can't figure out why so many people have so many issues with this stuff... :confused:
 
Figured I'd take a snap of things at the moment...



19 tabs, that's about average for me most of the time, RAM usage is right where it's expected to be as well based on how I've got things set up.
 
Holy Nutbunnies! I forgot how fast you get responses on [H] :D
Thanks for your replies!


drescherjm
- Yes, they do make 8gb ssd-s, mainly the older models are this small tho..
- I thought there were 3 types, NAND (the newest), Multilevel Cell (MLC) and 1-bit-per-cell Single Level Cell (SLC).. But The market has perhaps switched to NAND all the way by now..

- I'd love to get more RAM but when I bought my Asus P5KC mobo 3 yrs ago I thought I'd never need more than 4 gigs of ram.. In other words, my mobo doesn't support more than 4gb of DDR3..
- Chrome might not have a drop down list, but I keep like 8 windows open with tabs "few" enough to still see their titles..
- Yes, I leave Chrome Open. I also forgot to mention that I usually hibernate the pc, only shut down once a week..
- I do shut down the ridiculously large chrome processes :) but I keep ending up with them again (from other processes).
- I guess Crhome does have bad memory leaks..

Dude, where can I +Rep your answer? :D Thanks for the detailed post.
- I thought a RAMDisk would only be possible on 6GB+ of ram. But from your post I see that you can do quite a lot with just 1GB reserved for it. :)
- I don't think I will put the paging on the RAMDisk, it's quite large and might also risk OS crashes.. (ie with hibernation)
- Not all Temp folders can be placed within a 1GB RAMDisk.. Photoshop CS5 uses a crapload of gigs on multiple partitions..
- I will make a RAMDisk and post after trying it out.
"Hey, dumbass, you're leaving tabs open again, start closing 'em... or I will..."
LOL, yes, I do have addons for tab/session managing, actually, 2 of them. But when I'm working on a project I open 2-3 windows of 20 tabs each with info, about a half of which I keep coming back to. And all these besides the other couple of windows I always have open with all sorts of things I often check out or haven't had time to check out yet..
- I can't wait for Firefox 4 to come out http://www.geek.com/articles/chips/hands-on-firefox-4-beta-2010077/ When that time comes, it's firefox all the way! (Right now it crashes too much, and I hate it when that happens on 100 tabs)
- I will drag my portable browsers and whatnot from my flash drive and use them on my PC then.
 
I would LOVE to use Firefox but that just isn't going to happen. I didn't choose Chrome for its "speed" or any crap like that, I chose it because Firefox (and Opera, IE, everything not Chrome) are limited to a single process on a single CPU core. This wouldn't be a problem with normal websites but anything that uses Flash, which is a CPU intensive application, will bog down that single process and give me lag spikes. Spikes can commonly happen if I left a YouTube video on the finished state where it keeps refreshing related videos on the video frame. Each act of refreshing creates a lag spike for the entire browser (if it is not Chrome).

If only it were that simple though. How easy would that be? Just don't leave it in that state! If only YouTube was the only place Flash was used... The lag ends up happening regardless, I can have no YouTube tabs open and be scrolling down a page and it freezes for a moment during the scroll. The lag spikes make watching online videos very unpleasant. I may be wrongly or incompletely blaming Flash for these lag spikes because even with the FlashBlock addon blocking all but the desireable Flash elements, the lag spikes occur. I can SEE the browser process have a sudden large value for CPU usage at those moments. This happens on my desktop, laptop, dad's desktop, every computer. The solution is to use Chrome.
 
Yes, they do make 8gb ssd-s, mainly the older models are this small tho..

I thought most of them would be slow especially the ones from 2008.

I thought there were 3 types, NAND (the newest), Multilevel Cell (MLC) and 1-bit-per-cell Single Level Cell (SLC).. But The market has perhaps switched to NAND all the way by now..

The two types are NAND (not and) and NOR (not or) inside these these types you can have SLC or MLC.
 
Alright mates, I've installed RamDisk Plus and have made a 1gb ramdisk that doesn't get erased on shutdown and to which my windows temps and browser caches are stored.

I've moved a Chrome Portable in my RamDrive, pointing all of the offline data (settings, extensions, bookmarks etc) to the location in C:\Users\blaetc.

Things have indeed gone a lot smoother, it's great, but chrome processes still use quite a lot of memory...

At this point, I'm at 92% RAM, consisting of:
80 chrome tabs open (of which 6 short "youtube" clips),
the 1GB RAMDisk (out of which 800mb free),
a couple of dirs open, Pidgin IM and 7 other quick launch dohickeys..

Anyway, Chrome is using at least 2gb right now, spread through 20mb to 99mb mini processes, one 300mb one and one 200mb (both of which I will close).

Point is, is there any way I can reduce the amount of ram this browser uses?(since I'm running it off the RAMDisk?) If I maximize and reload a window, that window will get to 300mb on its own eventually and I'd have to stop it manually again... :( This sucks when I have other programs open as well..

--Oh and btw, it's never just the "one" window in one of these 300mb using processes. The tabs involved in such a consuming process always seem to be randomly spread through multiple windows. So it doesn't happen on just the one window I'm working in, but it's perhaps triggered by it.
 
Last edited:
It should happen the most on websites that like to refresh periodically on their own. Facebook is definitely one of them, weather pages, etc.
 
I would LOVE to use Firefox but that just isn't going to happen. I didn't choose Chrome for its "speed" or any crap like that, I chose it because Firefox (and Opera, IE, everything not Chrome) are limited to a single process on a single CPU core. This wouldn't be a problem with normal websites but anything that uses Flash, which is a CPU intensive application, will bog down that single process and give me lag spikes. Spikes can commonly happen if I left a YouTube video on the finished state where it keeps refreshing related videos on the video frame. Each act of refreshing creates a lag spike for the entire browser (if it is not Chrome).

If only it were that simple though. How easy would that be? Just don't leave it in that state! If only YouTube was the only place Flash was used... The lag ends up happening regardless, I can have no YouTube tabs open and be scrolling down a page and it freezes for a moment during the scroll. The lag spikes make watching online videos very unpleasant. I may be wrongly or incompletely blaming Flash for these lag spikes because even with the FlashBlock addon blocking all but the desireable Flash elements, the lag spikes occur. I can SEE the browser process have a sudden large value for CPU usage at those moments. This happens on my desktop, laptop, dad's desktop, every computer. The solution is to use Chrome.

Exactly! Chrome is awesome due to it's multithreading processes. Firefox eating one CPU core is horrible. It was great back in the mid-2000's, but not now.
 
It should happen the most on websites that like to refresh periodically on their own. Facebook is definitely one of them, weather pages, etc.

Oh yeah, you're right! I've always tried to link these mysterious tabs by thingking it's the plugin, ie tabs that use flash. But it wasn't right. Now I realise it's the youtube vids that have finished playing or the gmail or ajax pages perhaps etc..


One more thing, I've installed chrome portable on the RAMDisk, but each time I open it from the shortcut pointing to it's exe, the taskbar says (in Propreties) that it in fact opened the chrome from "C:\ProgramFiles x86" instead of the portable one.:eek:
Furthermore, if ChromePortable is pinned to the taskbar, when I open it, Windows automatically changes the Target of that taskbar item to chrome.exe from Phogram Files. :eek::eek:
If I rename chrome.exe from PF to chrome-bak.exe, it points to chrome-bak.exe:confused:
If I change to chrome.exe.bak, then it changes the shortcut to an "invalid" one.

Why the heck doesn't it allow me to run the portable? is it because I've set the portable to access the user data from the non-portable version's folder?
 
Blunt answer? Its because you're trying to do something unorthodox. Maybe get 8GB DDR2 instead? Sell the DDR3 you currently have, they are about the same price anyway. Net change is still -$80 for the entire operation.
 
Short answer is I don't believe it's wise to put your page file on an SSD due to the amount of writes that are done to it. Windows 'touches' the page file about once a second regardless of the physical amount of RAM you have. For an SSD that can lead to a somewhat reduced lifespan because a cell can only be written to a limited number of times before it dies. Keeping your swap file on an SSD *WILL* reduce it's life even with the most aggressive wear leveling techniques... how much that lifespan is reduced remains to be seen since the technology is so new there are no real-world numbers to rely on.

The same goes for Photoshop scratch files, web browser cache folders, etc. I would be wary or at the very least take notice of the amount of writing your SSD is doing. You want your SSD to spend 95% of it's life doing READS and not writes. It's my belief that putting these files on a standard mechanical hard drive would be a good idea if at all possible.

Perhaps I'm just paranoid... but again because it's such a new technology and expensive at that there isn't a lot of data out there short of speculation and heresay.

[EDIT: Re-worded my post to make it clear that this is MY OPINION and to clarify that point.]
 
Last edited:
The whole pagefile thing significantly reducing the life of an SSD is nothing to worry about. Sure it can reduce the life of an SSD, a little; as instead of working for 10 years it lasts 9.8 years.. Woopdedoo. Whomever mentioned "tenfold" is spewing scary words that mean nothing when tenfold is a "relative" number. A single intensive read/write benchmark (which everyone like to run on their new SSD's) works the SSD harder than 3 months of intensive pagefile usage. It is doubtful you will be using the same SSD for even 5 years anyway.

If you want to be anal, sure, put all your temp stuff on a HD. Defeats the whole purpose of using an SSD for its speediness, but hey, people do dumber things. Maybe if you have the cheapest, crappiest SSD, it might even be a good idea, as some of the early ones are slower than good HD's anyway. The only reason I can think of for not having the pagefile on the SSD is that you might have a really little one and you actually would rather have the 2-4 gigs of pagefile space used for OS/applications, but worrying about the life longevity of any current SSD because of the pagefile is foolish.


FYI:

NAND is a memory type that is used in all current SSD's. It has two main subtypes, SLC (single layer cell) and MLC (Multi Layer Cell). Most commercial SSD's use MLC NAND memory because it is allows SSD's to be much more affordable and larger, relative to SLC NAND memory SSD's. The downside of MLC NAND memory is that it does not have the write endurance (useable longevity) of the SLC NAND memory.

The general minimums for each subtype of NAND memory of write endurance is 100k write cycles for SLC and 10k write cycles for MLC. These are generally viewed as the "minimums". In actual operation though, most cells will far exceed these numbers and when cells finally do die, the controller will remap good cells around them.

You will generally see SLC SSD's designed for server type usage while MLC is generally commercial/retail type usage. The biggest SLC SSD's are only 1/2 the size of the biggest MLC SSD's yet tend to cost 3 times as much.
 
Lots of hubub in this thread....

Short answer is you shouldn't put your page file on an SSD due to the insane amount of writes that are done to it. Windows 'touches' the page file about once a second regardless of the physical amount of RAM you have. For an SSD that can reduce it's lifespan tenfold because a cell can only be written to a limited number of times before it dies. Keeping your swap file on an SSD *WILL* reduce it's life even with the most aggressive wear leveling techniques.

The same goes for Photoshop scratch files, web browser cache folders, etc. You want your SSD to spend 95% of it's life doing READS and not writes. Put these files on a standard mechanical hard drive when at all possible.

The only way I would ever put scratch files on an SSD is if I were a rich man and didn't mind replacing the SSD on a regular basis.

Microsoft recommends putting the page file on an SSD and doesn't mention reduced lifespan as one of the caveats.

I won't argue that a cell has a limited number of writes and that your SSD should be doing far more reading than writing in order to extend its lifespan. But reads to the page file outnumber writes 40:1, so that's good. Not that it still can't be written to a lot, but it'll still be read from a LOT more.

I'm not against placing my page file elsewhere (on a RAM disk or even a spinning disk). I'm willing to give up some performance if it means my SSD will last significantly longer. But I'm skeptical of your claim that placing the page file on an SSD will reduce its lifespan "tenfold."

If what you say is true, then users who keep the page file on their SSDs (the vast majority) should be showing vastly increased levels of wear. Why don't we ask them to post their wearout indicator numbers so we can see proof of this vastly reduced lifespan? I'm willing to bet that most of them using the drive in a normal manner are trucking along just fine with wearout indicators that are well within normal ranges for the amount of time that the drive was used.
 
Short answer is you shouldn't put your page file on an SSD due to the insane amount of writes that are done to it. Windows 'touches' the page file about once a second regardless of the physical amount of RAM you have.

I disagree. If you do not have enough ram putting the page file on a SSD is the best place to put it. The OS will not be writing every second to the page file unless there is some bug in the OS causing this horrible writing pattern. Or the user is using way too much memory. Pages that are modified that often should be in the working set and should not be paged out. If a page is not modified it will not be written also.
 
I disagree. If you do not have enough ram putting the page file on a SSD is the best place to put it. The OS will not be writing every second to the page file unless there is some bug in the OS causing this horrible writing pattern. Or the user is using way too much memory. Pages that are modified that often should be in the working set and should not be paged out. If a page is not modified it will not be written also.

I re-worded my post, but on the point of the OS using the swap file... I was referring to Windows in particular and I do stand by my original claim. Watch any Windows machine from 9x all the way to 7 and you'll see that reguardless of the amount of physical memory the swap file is touched once a second. You can observe it pretty easily...

I would like to point out (even though it means I have to eat crow) that my opinion is just that - OPINION - and I am fully willing to admit that I have very little experience with SSDs save for the occasional client machine. I am pretty frugal and haven't been able to justify the expense for myself, so my advice is coming from my learned understanding of the technology and it's fundamentals - not from experience and I am fully willing to admit that. Truth is there just isn't a lot of real world data out there yet but I personally would rather err on the side of caution.
 
No crow to eat Falcon, just people don't understand SSD's well yet.

Let's put things in perspective. As I said earlier, most MLC SSD's have a minimum write cycles of 10k writes before the cell gets stuck. So lets pretend we have a brand new 64GB SSD. If you completely over wrote the entire SSD with 64GB with 1's bits once a day, it would take 27.4 years (10k/365) before any of the cells died (assuming the cells only lasted exactly 10k writes cycles, when in fact they often last much longer). If you overwrote the entire 64GB with 1's "10" times a day, it would take 2.7 years (10k/10/365)before any of the cells started to die. If you overwrote the entire 64GB worth of data 100 x per day, it would take 0.3 years for the cells to start dying.

In the course of the average person's "typical" computer usage patterns, how many completely overwrite 64GB worth of data even once a day much less 10 times a day? Windows might look at the page file a lot, but it''s not "writing" a lot. Even if it was, it's not pumping 64GB of write data per day, so theoretically, the NAND is gonna last longer than 27 years at these write cycles. Thing is, even should a bunch of cells die from too many write cycles, the worst that will happen is the drive gets smaller in new-data write ability size. As they all die off, it would continue to shrink, until one day it becomes read only, but the data wuold all still be there, and in that case, you would theoretically just copy all the data off onto another drive and start over, but you are gonna be doing a helluva lot of writing to wear out the NAND on even MLC SSD's.

For those special occasions when an SSD does have to write that much (e.g. some custom server application) one then gets SLC SSD's, where the write cycle abilities of the NAND is at "least" 10 times higher than MLC NAND.

The only apps which tend to burn through SSD write cycles are benchmarks programs. The wear from the pagefile is nothing compared to the wear from benchmark programs. But that's what they are designed to do, write a lot and see how long it takes to do it and read it back.

SSD's "do" fail much sooner than 27 years, much less 10 years, however it is rarely because the NAND has been written to too many times, it will much more likely be the controller/ associated power regulation just goes bad, or perhaps the firmware corrupts, etc.

Worrying abuot the life cycles of the NAND memory under "normal" usage is like worrying about the engine of a car and neglecting to care aboutthe outside of the car where they use salt to remove snow on roads. The outside (in this case the controller or power regulation) is gonna rust/rot and fail before the engine gives out (memory).

In the real world of SSD manufacturing, consumer SSD's are expected to last about 7-8 years at best before something kills them, despite how much care you might take with the NAND memory write cycles. Why only around 7 years? Because technology moves too fast. How many people have a 7+ year old anything electronic device and haven't replaced it? Not many people want to keep using a teeny 64GB SSD if in a couple years, the starting point for SSD's is 3-5 times larger at 1/2 the buying price.. 7 years ago, 20-30GB hard drives were on the big expensive -side. How many people still use the 20-30GB sized drives today? The few that do, are the people who don't tax their PC's that hard anyway, in which case, an SSD will last a damn long time for them anyway.
 
Last edited:
The 8GB SSDs on newegg are ~$100 each, you can save money AND have a more guaranteed performance gain by getting more RAM. Assuming you currently have a 4 RAM slot mobo and 2x2GB DDR3, buy 2x2GB more. I similarly have issues with 4GB, its too little, I hate it. 8GB all the way, man.

What are you doing with 8 GB ??
 
DataRam makes a free one that works with Windows just fine, SuperSpeed RamDisk Plus is a commercial product that works great as well - that one supports a page file placed on a RAMdisk but again that's not my suggestion.

If you open the System Properties and look at the Advanced tab, there's a button near the bottom for Environment Variables which you use to reassign to new locations (the TEMP and TMP ones are all you need to muck with). Pointing those to a RAMdisk of about 512MB to 1GB in size will have a dramatic effect on system performance overall, not just for web browsers. Then point the browser caches to the RAMdisk as well and it just gets better and better.

:p

I'm using XP Pro, which only see 3.25GB of RAM eventhough I have 4 GB. Can Super speed RAM Disk see the remaining 0.75GB eventhough XP Pro can't?

And the above Sys. property/Adv. Tab, what ver. of software are you referring to?
 
The general minimums for each subtype of NAND memory of write endurance is 100k write cycles for SLC and 10k write cycles for MLC. These are generally viewed as the "minimums". In actual operation though, most cells will far exceed these numbers and when cells finally do die, the controller will remap good cells around them.

This was maybe true for old-style 90 nm NAND Flash. For 34 nm NAND Flash, MLC only has around 3k cycles. Since the drive voltage for Flash cells hasn't been decreasing, the damage done to the smaller cells keeps increasing, as well as the collateral damage to the surrounding cells and data.

As for the longevity of such a 34 nm MLC NAND Flash SSD when used for a pagefile, consider it writing a lot of 4k pages across the SSD, rarely in the same cell. Let's take a 128 GB SSD for example:

137,438,953,472 bytes / 512 kB blocks = 262,144 blocks

Let's assume a low 2 writes per second to different blocks. Keep in mind that one cell of a block dying means that the entire block is unreliable.

262,144 * 3,000 writes/cell = 786,432,000 writes max
786,432,000 / 2 = 393,216,000 seconds, or 6,553,600 minutes, or ~109,226.667 hours, or ~4,551.111 days. Basically just a tad over 87.5 years.

Of course, 2 writes/second is extremely low, and 4 kB extremely little pieces of which a lot will be needed for any reasonable modern data set or program. Let's try 1,000 writes/second for a good, solid swap operation instead, still involving only a tad under 4 MB/second:

786,432,000 / 1,000 = 786,432 seconds, or 13,107.2 minutes, or ~218.453 hours, or just 9.1 days.

In conclusion, putting a swap file which sees regular use on an SSD is a quick way to slaughter it, probably well within a year. You're much better off investing in a RAM disk. RAM isn't that much more expensive than NAND Flash anyway.
 
I'm using XP Pro, which only see 3.25GB of RAM eventhough I have 4 GB. Can Super speed RAM Disk see the remaining 0.75GB eventhough XP Pro can't?

And the above Sys. property/Adv. Tab, what ver. of software are you referring to?

SuperSpeed's RamDisk Plus sees the unmanaged RAM that Windows can't touch (when you're using +4GB of RAM and the 32 bit version of the OS) and allows you to use it for a RAMdisk, hence my situation. On my laptop, only about 540MB of the 4GB (the highest portion) isn't seen by Windows 7 Pro x86 so I have RamDisk Plus set up to snatch that unmanaged RAM as well as the rest to fill out the 1GB necessary for my RAMdisk.

As far as the System Properties, I mean this:

sysproperties.png


Click that then you'll see the TEMP/TMP variables at the top already assigned to the "standard" temp directory which is %USERPROFILE%\AppData\Local\Temp - you alter that path to point to the RAMdisk when you set one up (I always use R: for the drive letter for the RAMdisk and create a Temp directory on it for such purposes).

If you do that, your TEMP/TMP variables would then point to R:\Temp or whatever you've chosen for your RAMdisk and from that point on (after you click Accept and close that dialogue box), all system temp files and variables as well as any created by apps (unless specified otherwise by each app's own preferences or settings) will get sent to the RAMdisk.

You can then alter your browser's cache to point there as well, a Photoshop scratch disk if you want (and have RAM to spare because Photoshop is a RAM hog, always), whatever you want really.

And as much as I don't like to do it, I agree with Elledan above: if you must "do something" with your page file, get more RAM in the system and get SuperSpeed's RamDisk Plus (because I haven't found another RAMdisk that will let you do it, at least no free ones I can recommend) and create a static page file on the RAMdisk. There's always some discussion around here about this at various times, some folks say don't do it, some folks say do it, others say if your system is paging that much then you simply don't have enough RAM in the system in the first place, etc etc.

My response is that Windows was written from day 1 to use the virtual memory subsystem as a way of "doing more" than the physical hardware would allow for, primarily meaning you can do more with less RAM because it'll simulate RAM with the page file as required - but too many people think page file = virtual memory and while that's true to a very small degree, the page file in and of itself != (that means does not equal for those that don't get it) virtual memory. The page file is one small component of the entire virtual memory subsystem of the entire OS itself, and while the factory defaults for Windows are pretty damned efficient, you can do a few things to make it work even better like using a RAMdisk for a variety of purposes.

The suggestions I've given will provide you with a far smoother running and faster performing machine overall, so take 'em or leave 'em. You don't have to believe me, just grab the trial edition of RamDisk Plus from SuperSpeed.com and set it up and do your own testing, find out for yourself what a difference using such a piece of software and RAMdisks can have on your system performance, then make up your own mind as to whether it's working or not based on the testing results.
 
Last edited:
Xer0 & Elledan, thank you very much for your feedback, I was thinking of buying a small ssd just to use as a ram disk for the paging file, and if it lasts 3 years and the price is significantly(?) less than actual RAM then it'd be worth it imho..

HOWEVER, I noticed that a RAMDisk on RamDisk Plus of just 700MB for the temp environment variables and web cache is more than enough; so I think that I'm good for now.


You can then alter your browser's cache to point there as well, a Photoshop scratch disk if you want (and have RAM to spare because Photoshop is a RAM hog, always), whatever you want really.
Bahamut, I've got 2 questions:
Would say a 200MB Photoshop scratch disk on a RAMDisk actually do more than say 4-8GB of scratch on 2 mechanical HDDs? (does it work faster and dismiss sections quicker, or does it just fill up those 200MB and slow down?)

And second, I currently have a 666MB RamDisk Plus drive, set to be remembered and saved when rebooting so that I wouldn't have to format each time. I've also checked the "zero out" feature, but after I reboot, the RamDisk doesn't get cleaned out, it keeps temp caches from last session and I would have to delete them by hand.
How do you actually have it clean itself out?

One more thing: Is it worth it to have PART of your pagefile on a RAMDisk and still have a 2GB part on C for example?
 
Let's see here:

Leave the scratch disk on the RAMdisk - no hard drives on the market today and certainly no SSDs either (even if you RAIDed 10 of 'em together) can match RAM's access speed and bandwidth. If you're dealing with massive images, however, ones that require far more than 200MB of space on the scratch disk, then you can use multiple scratch disks spread across multiple drives and get that boost from multitasking ability while still getting some benefits by using the RAMdisk - some of that temp data will hit that RAMdisk and when it does it'll be lightning fast.

There's realistically no reason to "mirror" the RAMdisk to the hard drive so it gets saved at shutdown and restored at boot time unless you're putting some portable apps on the RAMdisk. If you are only using it for temporary file storage, stop the mirroring/backup aspects - it's not necessary, and it just makes shutting down and rebooting slower. To create and format a RAMdisk takes like 1/2 second - to save the contents at shutdown takes a lot longer, and when rebooting the restoration process just adds a lot more time to the reboot cycle, so it's simply unnecessary.

If you're not going to save the contents for shutdown and restore them on reboot, there's no reason to use the "zero" option either. As soon as power is tripped in the system on the reboot, all that data is wiped from RAM with the refresh anyway.

I myself DO use the backup/restore option because I have a bunch of portable apps on my RAMdisk (Firefox, etc etc) and so I do want that stuff saved and restored on a reboot (which is maybe twice a week unless some update or whatever actually requires it).

As for the page file thing again the only thing you can do with that system (aside from adding more RAM, maxing it out if you can) to improve performance with respect to the page file is put a small static page file on every single physical drive you have, maybe 1GB on each one. If you have 3 drives, that's 3 page files, and it allows the system to multitask better because it can read from one and write to another simultaneously as required, even read from one and write to two others if needed.

Anything you can do with a system that allows it to do more at any given time is a positive thing - spreading page files across physical disks is one sure fire way to ensure a system runs a helluvalot smoother and more efficiently. And of course, maxing out the RAM potential helps as well.

Do that instead of attempting to use the RAMdisk for any paging aspects... that's my suggestion.
 
To answer the topic: YES the pagefile should go on SSD. Analysis discussed here about a year ago shows that most pagefile operations are reads and, regardless, paging is secondary memory and should be FAST. People buy SSDs for speed, not to keep them "safe in the box" for 5+ years like action figures or comic books (which are also meant to be played with and read, respectively, but I digress). Also IMO it's a far larger waste of the SSD's ability to make sure that WoW and COD4 are installed on it but not your OS, pagefile etc... because you're afraid of "writes".

To comment on why you're asking: Get some more memory, and don't waste your time/money on an 8GB SSD. As long as you've go an x64 OS you'd be better with 8GB more memory so that you didn't need to page out the data in the first place. If you get an SSD, do yourself a favor and use it as your entire OS/System drive and enjoy the performance boost. Wait for them to go on sale/MIR or something - there's nothing wrong with saving money.
 
Allright mate, thank you, now I get it! :)

I did notice how ridiculously faster formatting 1GB of ram is compared to HDD space ^_^
And there should be a way to write a script that would automatically format a certain partition on startup. A batch file added to the startup tasks.. If you haven't done that already, I'll look into it, shouldn't require too many lines of code.
 
What are you doing with 8 GB ??
Chrome, AIM, VMWare, Word, Excel, Photoshop, WinSCP, Notepad++, PuTTY, MPC-HC, <EDIT>Windows Media Center, </EDIT>and foobar2000 should be all the applications I use on a regular basis that I can think of right now (not using desktop atm). I commonly see the RAM usage at 5-6GB, making 4GB RAM simply too little.

I know a lot of you think 4GB is enough (which is false btw :p) because I get your reaction a lot. Does it make you feel better that I got my RAM back in December 2008 when 4GB DDR2 was $15 AR?:p
 
Last edited:
Chrome, AIM, VMWare, Word, Excel, Photoshop, WinSCP, Notepad++, PuTTY, MPC-HC, and foobar2000 should be all the applications I use on a regular basis that I can think of right now (not using desktop atm). I commonly see the RAM usage at 5-6GB, making 4GB RAM simply too little.

I know a lot of you think 4GB is enough (which is false btw :p) because I get your reaction a lot. Does it make you feel better that I got my RAM back in December 2008 when 4GB DDR2 was $15 AR?:p

I'd use FileZilla instead of WinSCP, it's in the top 3 most downloaded free softwares of all time, according to some source I don't remember :p


I'd really hate to downgrade from DDR3 1333MHz to DDR2 @ 800 or smth.. just to get more ram :(
Aren't there some sort of PCI RAM drives that would be the next best thing? Anyone know more about those?
 
There are such devices, but because they attach to the machine on PCI-Express cards, they don't work like RAMdisks do nor do they offer the performance a RAMdisk is capable of. They're basically making cards with lots of RAM slots on them you populate with high speed RAM and then it's "seen" by the PC as another SATA drive that ends up basically choking the shit outta the bandwidth they're capable of. Whereas RAM in most machines, especially DDR3, is capable of multiple gigabytes of bandwidth per second, even multiple SATA drives (even SSDs) are still barely going to get close to a full gigabyte per second of potential bandwidth sustainably and reliably). RAM can do that shit 24/7 without breaking a sweat and no "cells" to worry about damaging with multiple write cycles... ;)

Those devices, like the Gigabyte iRAM, etc, only offer high transactional rates and very low access times, but that doesn't help much when you're still basically stuck at SATA speeds for real transfers. Yes, it's "better" than a physical hard drive but, buying more RAM for the machine is still going to be a better solution. I'd take 8GB of DDR2 over 4GB of DDR3 anyday and twice on a Sunday because I can get more use from the increased amount. The so-called speed differential in there rarely actually provides any seriously useful performance benefits.

More RAM is the best way to improve overall performance on any modern computer - not a faster CPU, not faster storage, not faster video cards, only pure RAM can do that, as much as you can put in a given box...

<and then actually making that RAM useful, of course...> :D
 
Last edited:
I'd use FileZilla instead of WinSCP, it's in the top 3 most downloaded free softwares of all time, according to some source I don't remember :p


I'd really hate to downgrade from DDR3 1333MHz to DDR2 @ 800 or smth.. just to get more ram :(
Aren't there some sort of PCI RAM drives that would be the next best thing? Anyone know more about those?
http://ixbtlabs.com/articles3/cpu/ddr2-800-vs-ddr3-1333.html
8GB DDR2-800 will FAR outperform 4GB DDR3-1333. As Bahamut stated, higher speed RAM makes very little difference. Look at the article I linked. The differences, if any... are what, less than 1%? OOooOoOo I want 1333MHz already!;)
 
I say go with 8 gigs of ram than look for an 8 gig ssd.
With the 8 gigs ram you can use ramdrive and allocate 1-2 gigs for your browser's cache.
I put IE ache on 1 gig of system ram and everything opens instantly!
 
RAMDisk 11 Plus sure does want a ton of money. $99.95 for their product.
Nice additional features:
Compressed image file for faster image loading
Save RAM disk image automatically at system shutdown option
System page file support
Support for Virtual and Removable RamDisks
-- Maybe it works on VM's in Workstation 7?
This company looks like they have more corporate buying for using their product on servers.

DataRAM product RAMDisk is free as mentioned but the "buyin" is much less at $9.99. This purchase really only allows you to move the RAMDisk capicty beyound 4GB. Not too many people out there that have 16GB installed on their mobos. That option probably isn't needed for most desktop users. I doubt many people have massive SQL tables that need to remain in memory.

Features
RAMDisk is also great for storing frequently accessed data such as temp files, page files and database index files.
YOu can start a second instance of any OS from RAMDisk using VMWare or other Virtual OS tools.

For free you can get the pagefile in the ramdisk if you so desire.
 
http://ixbtlabs.com/articles3/cpu/ddr2-800-vs-ddr3-1333.html
8GB DDR2-800 will FAR outperform 4GB DDR3-1333. As Bahamut stated, higher speed RAM makes very little difference. Look at the article I linked. The differences, if any... are what, less than 1%? OOooOoOo I want 1333MHz already!;)

Damn it, they're right! I won't be needing DDR3 on my Q6600 at all then.. Anyone wanna trade their 8GB DDR2 for 4GB of currently "useless" DDR3's? :D
 
Damn it, they're right! I won't be needing DDR3 on my Q6600 at all then.. Anyone wanna trade their 8GB DDR2 for 4GB of currently "useless" DDR3's? :D
Hopefully these links work.
http://www.newegg.com/Product/Produ...66&IsNodeId=1&bop=And&Order=PRICE&PageSize=20
http://www.newegg.com/Product/Produ...66&IsNodeId=1&bop=And&Order=PRICE&PageSize=20
DDR2 and DDR3 cost the same, you would have to find a big chump in order to pull off your 8GB DDR2 for 4GB DDR3 trade.
I would try to sell off the 4GB DDR3 for as high as possible ($80 would be amazing :D) and then buy two pairs of 4GB DDR2. That would result in a net change of -$80, like I said before. I'm betting that it'll be closer to -$100 supposing a more realistic 4GB DDR3 selling price of $60.
 
I was waiting for a thread like this....

I posted this pic in another thread around dec 24, 2009 when I first picked up my Intel 160G2.

So i've had roughly 7 1/2 months worth of use on my SSD. I did use alot of the tweaks suggested so Page file has never been on my SSD, Firefox disk cache disabled, Indexing disabled, etc etc.

Here is a screenshot I took when I first got the drive after maybe a couple weeks of use and maybe 2 OS installs.



Uploaded with ImageShack.us


Here is my current host writes as of today August 5, 2010.



Uploaded with ImageShack.us

There are quite a few people that are like don't worry about it you will get rid of the drive before it becomes an issue. Well when I paid $500 for this drive I think i'm allowed to worry about its use and longevity. And to each his own if you are happy with the Page file being on there so be it but I wasn't.
 
Last edited:
Back
Top