Indexing and Page File on SSD

Well, I've now reinstalled Windows 8 again and it's working much better this time.

I've decided this time to just leave things alone! Page File is set to System Managed on the SSD, and Indexing is enabled.

The SSD has a 3 year warranty. If for some reason it fails in this time, I'll just send it back to Samsung. This whole laptop is 2 years old now anyway, and it'll be 5 years once the SSD warranty has expired. I'll almost certainly replace the whole machine before the SSD dies.
 
THIS IS MY CORRECTED POST Hopefully Webmaster has found time to remove my first post. I do not mean to post twice

OK, my post...SSD stuff...

I know the thread stopped receiving posts back in February. Was not sure if reviving it is ok or should a new thread be started? Someone feel free to let me know.

I have to say there are mixed ideas about the best way to optimize an SSD. Pagefile , disabling indexing for the SSD, and using Samsung Magician or choosing to remove it.

All this is because we do have a new wave of SSD drives, as well as OS improvements that have been ongoing since Windows 7. A lot of the suggestions for SSD optimization are a bit dated, I believe. Driver files that offer an install path can always be installed on the HDD because any required files that are configured in the registry will go to the proper windows system folder. INF files always go to the INF folder. Any other files that end up going to the desired path on your HDD are not files that are required by Windows to be on the root drive. Just remember that because often people ask if it is OK to install a driver on the HDD and the one who answers almost always says NEVER or might also answer by saying "Driver installation does not give you an option for install path". Exactly right. Most drivers install with no option. But others, like AMD Catalyst, will offer an option. But, the files that need to be in the Windows subfolders will be put there regardless. I have already done it and I think this is good information for a lot of people.

OK. I have a couple Samsung SSDs. Samsung Magician Software can be very effective, but I think it is best if used with a bit of knowledge about SSDs. Samsung's preset options, such as MAXIMUM PERFORMANCE, does not correctly configure my SSD to a level that I would agree is, "Maximum Performance", although it comes pretty close. Seems there are cases where some of the optimization techniques are very good choices in some situations where other specific configuration methods are just not as practical to one user but can greatly improve someone else's performance. As for Samsung Magician, I prefer to use the ADVANCED option because I seem to get more control over each individual option. But I cannot figure out if the option is "ENABLED". I see ENABLED next to each option, but is it already ENABLED or do I have to click APPLY in order to ENABLE it? It is very unclear to me if Samsung toggles the feature to ENABLED or DISABLED when I click APPLY, or is the feature already toggled based on what it already shows to the far right of each option? I have not figured it out so what I did in Windows 7 is searched online to find the method to manually address each option offered within the Samsung Magician software. I just think Samsung software was hyped as if it was the greatest thing out there but in fact I think the software only offers a couple nice features. One is the option to enable the Speed Boost which significantly improves the read/write speeds and I like the hardware optimize and performance test. I would prefer to do my software configurations manually because when I chose to learn how, it also taught me what these features meant. It means something to improve the performance of hardware but that deep understanding helps me understand why in some cases a different setting matters

OK, now there are a few options that people do not agree on. Pagefile being enabled or disabled. Also, should we disable the backup/restore data. And one person I recall asked if the pagefile would be best kept on an HDD instead of the SSD boot drive. Pagefile, or backup/restore data on the HDD, instead of the SSD boot drive seems like a nice idea, IMO. Can we do it? I will be looking into that because if possible, I would do it. Why do we want to keep saying YES to storing files data/files on the SSD when performance is not affected by storing it on a HDD(secondary data drive)? I would prefer storing as much data as possible on the secondary HDD. It gives the ability to use that free space on the SSD for something much more important. You might want to install Windows 9 on the SSD boot drive, & keep your current Windows 7 or 8 installation. If you keep as much free space on the SSD, you will have a better chance of being able to do that. I am using Windows 8.1 now but my Windows 7 is still an option when I boot. But I have it on it's own SSD. I have 2 SSD boot drives each 256GB Samsung EVO and PRO, 1 SSD work drive for my music production software samples on my Seagate 600 series 480GB, and 2 HDD 1TB WD Blue 7200 and a Seagate 1TB 7200 which are both data and file storage only drives

I do not agree with the comment I read from one user that suggested something like this:
"an SSD was meant to be used and that if the space required to keep a pagefile is an issue then buy more space"

Some people do not have the luxury of "BUYING MORE DISK SPACE", so I will never tell anyone to refrain from trying to find ways to free more space on their SSD boot drive. Nothing wrong with a plan to put data or files on the HDD instead of the SSD boot drive. I think there is a lot more wrong if you think you should let everything occupy the SSD. That mentality will eventually fill your SSD with programs/files that offer NO advantage and are just taking up space. If you already own/bought a second HDD, then you already "BOUGHT MORE DISK SPACE", so why not use THAT instead of wasting space on the SSD?

When someone here asked if storing the pagefile on the HDD was a good idea, a response I read was: "ABSOLUTELY NOT"? Seriously? That mindset leads to people not caring if everything is stored on the SSD boot drive. Put the pagefile and the backup/restore data on the HDD and then you can keep a pagefile AND the back/restore options active, instead of disabling those features like many SSD enthusiasts recommend. That gives you the convenience of those features while not affecting available space on your SSD. Is that not a WIN WIN?

"INDEXING" we are told to disable. This is something I think works for some and is utterly useless for others. Look at your needs. Are you searching your drive through hundreds of thousands of files throughout your day? If not, then disable indexing. There's no need for it. It's a wasted process. If you like searching your local drive with amazing speed, there are many 3rd party search programs out there that can be installed on, and ran from, your HDD, and are much faster and more powerful than Windows search. This is not even my opinion. It's a fact.
If you to index anything, only use it if you have an excessive amount of files stored in a particular folder. ex. enable INDEXING for your Documents folder (most files are document type and stored here) or, use an indexed search(or enable in windows is fine for an average user) only in locations where you stored your files. NOT the entire drive. A good habit and keeps a drive nice and clean

And we are also told do NOT defrag your SSD. However, Windows 8.1 has improved the Defrag tool(now called OPTIMIZER) and it knows how to optimize an SSD. But Using the original DEFRAG in Windows 7 is just a big DON'T. Optimizing an SSD is a more simple process if the drive supports TRIM, so older SSDs this need not apply

The term TRIM is defined as a "storage level hint". In the Windows 7 OS the NTSF file system sends trim hints every time files are deleted or moved. SSDs acknowledge these hints in Windows 7 for the most part, and the SSD is supposed to perform cleanup (reclaim storage, which clears the blocks that were once occupied by files) in the background to prepare for future writes. However, if the SSD is really busy, it might ignore a trim request or hint and this leaves blocks in limbo, that should be ready for new data to be written. This is why using Samsung Magician made sense in Windows 7, but on to Windows 8.....

In Windows 8, the new defrag(OPTIMIZER) detects volumes mounted on an SSD – During idle time, TRIM hints are sent for the ENTIRE volume. OPTIMIZER allows SSDs to acknowledge ALL trim hints & performs cleanup on ALL blocks leaving no trace of any deleted files, and further optimizes the SSD, making sure all the free space is accounted for. What was happening in Windows 7 when SSDS are too busy, blocks that should be marked as writeable are not available until a proper cleanup utility is used. Unless you are using Windows 8, you are foolish to remove Magician Software from your computer. There are no other options as far as I know, except upgrading to Windows 8 and letting WINSAT configure your drive.

WINSAT optimizes a volume mounted on an SSD. It will tell Windows the drive is in fact an SSD and optimize it as such. My experience score improved drastically when I let Windows 8 WINSAT optimize my SSD. Samsung Magician is still usable, but I think it should be used only by knowledgeable people who can understand what all the settings mean. Choosing the ADVANCED option to manually configure each option in Magician is likely to give a more defined optimization. But, WINSAT will be just fine, especially for those who are not very comfortable or sure which settings to adjust. I want to find out if moving my pagefile and backup/restore data to my HDD is possible. That seems very practical and a good idea, but that remains to seen. I expect it will be not only be possible, but a wise decision. Getting the most out of our SSD is the key, right?

OK. I opened a new book here. I do not intend to offend anyone for their opinions, and like to discuss openly, the ideas and options to better optimize a system using an SSD and for some a second HDD/data drive. It is really a challenge and there are certainly changes in hardware and also software within the OS, that warrant a better, more clear explanation, and understanding, into the many options we have when optimizing an SSD boot drive while maintaining the best performance based on each individual scenario. I think some of the old ideas may need revision and I also think we need to consider some of the newer ideas and count them as important too.(ex. pagefile, backup/restore data location options)

Bottom line, there is alot more information that is more current, regarding SSD setup and Optimizing for the best performance for each user. But, knowing what each of the options represents when configuring an SSD, understanding how each options will affect your computer configuration, and knowing exactly what you want to achieve, matters more than doing something just because someone else told you to do it. That means, what is good for me, may not be what is good for you
 
I disagree with so much of what you said, I really don't know where to start. And really, I really don't want to address all, but I will address a couple things.

First and foremost, Windows 8 (or 7) is not XP and what was good for XP probably is not good for W7/W8. You call for old ideas to be updated, but it seems clear you are still stuck in the past - at least in some areas. :( I think you should have done some more homework before posting. :(

1. No such thing as a Windows feature called Speed Boost. If you meant ReadyBoost, that is fading away for a reason; it is for systems with low amounts of RAM. But RAM is much more affordable than in the past, and 64-bit Windows and gobs of RAM are common on new systems. And IIRC, there is no "Speed Boost" named feature in Samsung Magician either. And of course, that Samsung program is for Samsung SSDs.
2. An SSD is an ideal location for the Page File.
3. Indexing should remain enabled on W7 and W8 for faster searches. Yes, on a new system, Indexing can take some time, but on a modern OS (which does NOT include XP) the Indexing process has been greatly improved and is smart enough to step out of the way when the user is not idle. Remember, W7/W8 are not XP.
4. The defragger in W8 is disabled for SSD - regardless the partitions or volumes on it.
5. WINSAT does not optimize anything - especially volumes on SSDs. And WINSAT only works for the boot drive. WINSAT provides a score so users can compare performance.

I think there is a lot more wrong if you think you should let everything occupy the SSD. That mentality will eventually fill your SSD with programs/files that offer NO advantage and are just taking up space.
6. That is downright silly, and wrong. Using that same "mentality" why store any programs on any disk? They will only take up space. Just keep them on CD/DVD or "the cloud". :r1:

Hard drives are electromechanical devices. That means they have moving parts and are much more susceptible to friction and wear and tear, not to mention mechanical defects. SSDs are much more reliable long-term storage devices for our precious files. And you are absolutely wrong to say there is "NO advantage" to storing programs on a SSD. Simply wrong! :frown6:

I do not agree with the comment I read from one user that suggested something like this:
"an SSD was meant to be used and that if the space required to keep a pagefile is an issue then buy more space"
That is NOT what was said. You cannot misquote then say you don't agree. Please quote or paraphrase accurately. I said, "I HIGHLY URGE you to free up space or buy more space".

And I stick by that for several reasons. First, again, the SSD is the ideal place for the Page File (if performance matters) as explained via the link provided in post 7. And because of that, if your drive (SSD or HD) is so crowded that proper PF operation is not possible, then you need more disk space. PERIOD! And to get more disk space, you either have to "free up space" by uninstalling unused programs or by moving files to a different drive, OR you buy more space. And frankly, buying more space makes more sense because simply moving files or uninstalling unused programs, in most cases, is just a temporary solution to the problem - and that problem is, there is not enough free space.

Yes, it is true that SSDs still cost more than HDs. But prices have come down significantly such that a 256Gb SSD can be had for under $110.

HDs will go the way of the floppy. IF budget allows, I see no reason to NOT use SSDs on your computer for your boot drive and to house all your applications. If budget does not allow for all SSDs, then I recommend a 256Gb SSD for Windows, drivers, major application files, and the page file. Then get a HD for backups, tunes and videos, and the such. Or for fairly decent compromise, get a hybrid drive - a HD with SSD buffer.
 
Stuck in the past? I was only discussing newer hard drives on new OS platforms, NOT XP. I think that XP and SSDs would be a perfect example of the past


I never said Windows had a Speed Boost feature. If you interpreted that because of improper wording, my apologies. I meant the feature in Samsung Magician to boost the speed of Samsung Drives and yes there is a feature to increase the speed within the last 2 revisions of Magician but you would probably not know since you uninstalled it. Only limitation is it cannot be used on multiple drives so it works great on my SSD boot drive.

I never said I know anything about how well a pagefile will work if on the HDD but I said I want to find out. BUT, I said I think it is something I would think is a good idea which is an opinion which you seem to have trouble accepting that others would want to have. You know your way is NOT the only way and if you could see past your own nose far enough you would know there was no harm intended when I made any comments. Simply that I did not agree with something you may have said but you seem to have trouble allowing someone to have a different opinion that might actually be better than yours because your situation is not the same as mine or maybe someone else.



Now your patronizing me. You like to express your views which I can be perfectly fine with that. But you need to learn to accept the views of others. You are, IN MY OPINION, NOT the expert of ALL THING SSD. My mind was open when I posted my message. You just have to be right all the time correct? Well you are right about some things. But please do not try and say that I even hinted about storing data on the cloud or a CD or other means which I NEVER mentioned. I said a secondary HDD in the same system. Maybe you should make sure you do not misquote what other have said when you make your slick condescending remarks. Let others live man. You are not the only one on the planet who has used an SSD and optimized it with good results. You do not know my situation or that odf others so open your mind a little instead of playing GOD.

I won't indulge in replying to you again. I was looking for a nice open minded discussion but you took offense, and that was something I specifically said I did not want to do here. But you only read what you wanted to read and took the liberty to try and embarrass me while making a fool of yourself. That shows very little class. Please do not reply to me again. I cannot deal with people that cannot appreciate others and what they think.
 
And in Windows 8.1 the Optimizer is enabled by default and WINSAT runs after OS installation at the first chance it gets, which is idle. If you have Windows 8 you have to manually configure it. Oooh, something maybe you did not know? How about a little humility. I do not expect it, but just in case you do not know or even think it is true, I am quite capable of managing my SSD without using all of your recommendations. So please do not reply as if you are teaching me something. Roll your eyes elsewhere
 
My stuck in the past reference was primarily due to your suggestion that Indexing is a waste of time and should be disabled. That was true for XP, but not for W8.

I didn't spend 24 years in the military defending your right to express your opinion only to stop you from posting it. But I do take offense when you misquote what was said, then try to convince others what was said was wrong. That is just not cool! And sadly, you are still doing it! For example, I never said you were pushing CD or cloud storage, but you sure made it out as though I did, then implied I did the misquoting. :(

This is a technical support forum where we discuss, among other things, technical facts. If someone posts inaccurate facts, that is NOT helpful to our readers. You posted inaccurate facts! Facts are not opinions. You cannot post your opinion then pretend it is fact, then whine and cry about your rights being trampled on when someone points out the truth.

You said storing programs and files on a SSD offers "NO advantage" and are "just taking up space". That is factually WRONG!!! And me posting the correct information has nothing to do with your opinion, or mine! It is about providing accurate information to our readers.

Patronizing? Not my way but if it appeared that way, then I too apologize. But note these are not two-way discussions but open for all (with all levels of expertise) to follow. Therefore, when I post, I try to word my posts so all reading, now and in the future, can understand. Does that mean stating the obvious? For some. But that is not patronizing or condescending. "Know your audience" when writing (or speaking) is key. It is simply understanding there may be many reading and these folks come with all levels of experience. So as helpers, we write with that understanding and it is up to each reader to understand and accept that too.
I never said I know anything about how well a pagefile will work if on the HDD but I said I want to find out.
What? Page Files have worked fine on HDs forever - decades, anyway - since Windows 3.0, long before SSDs. If you mistyped and meant SSDs, again, I provided a link that explains in technical (but not too deep) terms why the SSD is ideally suited to house the Page File. And why did I provide a link? Because I DON'T expect everyone to take what I say as Gospel, just because I said it.

Fact: I don't like to be wrong - especially when providing technical advice.
Fact: If I am wrong, someone will surely point that out.
Fact: Because I don't want to give bad advice, I do my homework! I verify my facts before posting. And I provide corroborating evidence so readers can see for themselves, and don't have to believe me just because I say so.

And contrary to another of your misquotes, I have no "trouble" relocating the PF to a secondary HD or SSD. But if performance is your goal, put it (and your OS and program files) on an SSD as the primary (boot) drive. If there is not enough free space on the SSD for Windows and the PF to operate unrestricted in, then you need to free up or buy more space - or compromise performance. Those are the facts, not my opinion. My opinion is, the best solution is to buy more disk space, then free up space on the boot drive so there is 20 - 30Gb of free space available for Windows and the PF to operate freely in. This allows lots of space for OS temp files and the expected expansion/contraction of the Windows managed page file. If you are not an expert at analyzing virtual memory use, let Windows manage the PF.
And in Windows 8.1 the Optimizer is enabled by default
For TRIM but not for defragging - that is disabled! Big difference and my apologies for not being clear on that before. Because of the way data is accessed with SSDs (directly, instead of by a moving arm positioning the R/W head of the HD over each storage location, sequentially), fragmentation is not an issue with SSDs. Yes, you can force defragging on SSDs with 3rd party apps, but again, because of the way data is accessed on SSDs, all defragging does is introduce unnecessary wear and tear. Defragging a SSD does not improve performance or free up space.

And no, I am not an expert on SSDs - which is why I included a link showing why the SSD is the ideal place for your PF. You however, feel perfectly comfortable insinuating you know more than others, making statements of fact that are not true, not providing any supporting evidence for your false claims, and claim you don't need any teaching because you know what's best. :(

If you follow the link in my sig, you can decide for yourself if I might know something about computers, and hardware in specifics. That said, in all my years the one constant has always been, "there is always more to learn!". So if you can "show" where my facts are wrong and yours are right, then PLEASE, teach me! I am here to help, but the icing is I get to learn too.

if you could see past your own nose far enough you would know there was no harm intended
??? Where did I say, suggest, or imply you intended harm? Or for that matter, where did I say ANYTHING about ANY "harm"? This is just nonsense.

I am sorry, tteksystems, but it is clear you are the one who turned the tone of this thread, and it is you who took it personally when information presented was counter to yours, then fabricated falsehoods, and launch personal insults, like "looking past nose", "playing GOD" and show some "humility".
 
I really do not want you to take this personally. I'm not trying to be insulting, but you have this obvious arrogance in your wording that gives the impression you think you are better than others. Please don't elaborate or dignify this with a response. It's an observation that might be due to words not correctly representing who you really are.

I have to say that you are right about a few things. But you're not even interpreting things in the way they were implied. And please do not elaborate on this either. No reply, please. You take things in such a literal sense, that you leave no room for discussion by the manner in which you reply. This is a tech support forum. But you have expressed this type of mannerism that has you in dispute over a few differences of opinion and try to say that your view is a FACT. Again, no room for discussion, because your statements have to be correct but still, you are not speaking facts, except by your OWN experiences. Your not making any concession for exceptions to the rules that you seem hard pressed to bend. All things you say are facts according to you. But you still miss the point because you are too anal about it. And then you have to use this comment about being in the military for 24 years to defend my ability to have an opinion but not so I can express it? And if I did not quote that word for word from your previous message, you come back and accuse me of misquoting. There is no winner in forums when tech support issues are shared so others can learn but you break apart my messages in sections like you are dissecting me and passing judgement which would piss anyone off. You don't leave much room for a discussion about something and you only insert replies to a specific section as if the entire message is not important in understanding the entire scope of what I originally intended by trying to enter this forum in the first place. It was not a message to say I have all the answers, & it was not a plea for someone else to come in and dissect my words and count my opinion as some foolish idea.

You can store a pagefile on the HDD. Yes, you finally admit there is no problem doing it. So why do you think that it is best kept on the SSD boot drive? Well, you can say it is best to do so but I say no it is not. But only in MY situation. You, however, have a different agenda with your system and you do things differently because you have optimized your rig around your needs. Why you acting as if my agenda is anything like yours? I have an agenda that putting my pagefile and every stitch of data possible on my secondary HDD? My agenda is to free up as much SSD as possible and I want my pagefile as well as every other file to reside on a different drive, if possible. Nothing wrong with it. You go for the throat with your replies and come off like a know it all that has nothing to prove as if others could not rival you and the knowledge you possess. Don't pretend it isn't true. I am not alone regarding this revelation.

Performance does not change on my system when storing my pagefile on my HDD. So your comment does not hold water. You know, .......the comment where you said something to the effect that performance is better if the pagefile is on the boot drive. Well, I suffer no performance loss at all. My system is more than capable of cruising at top speed in this scenario and, it gives me more space on the SSD> FACT, the more free space on a drive, the faster it goes.

You like throwing around the words and opinions expressed by me, and if you have a problem with something I said, or a different opinion, you come storming out on the message board and throw a fit like someone just slashed your tire. I am not the least bit interested in your military career, and still cannot figure out why you even made a reference to that. Frankly, you're not a good person to have an open discussion with because your views are too strong and your opinions are strict. There is no way I would believe that anyone could ever teach you anything. And if Anyone, including me, learned anything from you, we probably would not like the method of delivery you use when you bring something to the table. Not to mention, if anyone else brings anything to the table, you are likely to return it because you are not easily satisfied. It the impression you give. I think you are the type that has to get the last word in so I expect you'll reply to this post. But, it has to be my last. I have to get busy and I've got to get to a forum where there is an ongoing discussion about the latest SSD drives running in the newer OS environment. That was my original agenda. I do not want to deal with broad discussion that leave room for someone to chime is and throw XP in the mix and if what I am doing would not work in an older OS, the sh*t hits the fan and all my up to date information that is relevant is challenged by some anal idiot who thinks he knows it all. That was sarcastic. Sorry. Really, I mean that sincerely, sorry.
 
tteksystems, chill.

When it comes to paging files, there's no right or wrong way; no matter which route you go, the vast majority of PC users with a reasonable amount of RAM installed will simply feel no difference in performance.

Even Mark Russinovich has changed his tune on page file sizing some 3 times, maybe more, and that's just where he was trying to generalise - for the majority of users.

When you bring SSDs into the mix, especially in a multiple drive setup, it becomes way more complex; on my own machines, I've changed the page file sizes some 4 times on my main PC since #5 here, simply because my workload is frequently changing; it doesn't improve performance, it might cost me a minute or two per day - but it does allow me to get a little closer to feeling what's happening with the main bottleneck in the system.

Likewise, there are times when I lock my CPU maximum frequency down to the minimum for several days at a time because there's no heavy number crunching that needs to be done.
 
You cannot lash out, insult and slap someone in the face, then tell them not to respond and expect them not to. To me, that's arrogance! I provided supporting evidence to support what I said. You just expect others to accept your comments. Again, to me that's arrogance!

I say again, this is a technical forum for technical facts. When writing technical papers, there's no place for personal emotions. It is all about the technical facts. Yet your concern is all about your feelings being bruised rather than ensuring you are providing accurate information to YOUR readers. That is sad, IMO.

Technical writing should be concise and to the point, leaving no room for personal feelings or interpretation to get in the way. That requires a "matter of fact" approach that can be interpreted as arrogance, IF the reader reads-in emotions that are not present. IF you could "see" the writer's facial expressions and body language, and IF you could "hear" the speaker's tone of voice, then you might be able to accurately "read between the lines". But you cannot do that in technical writings and therefore you must not interject emotions that are not there. If you let your emotions get in the way, and you insert things that are not there, it may sound like arrogance, but it is certainly not intended that way. And more importantly, you then miss the real message.

"Pride of authorship" is one thing - but there's no place for emotion in technical writing - especially when incorrect information is presented.

Successful communications is a two-way process. The sender must say what he meant to say, not leave it up to interpretation or conjuncture. That is, "literally". The sender MUST know his audience. And the recipient must not read into the message emotions or points that are not there.

I am sorry if I hurt your feelings (and I mean that sincerely), but I do not apologize for ensuring our readers have the true facts. I see that as my job here.

You can store a pagefile on the HDD. Yes, you finally admit there is no problem doing it.
:censored2: See? This is the BS I am talking about and will not tolerate, or stand by and ignore. Finally admit? I NEVER said anything to suggest PFs cannot or should not be on a HDD. I said repeatedly for "best PF performance", put it on the SSD. Why? Because, as noted in the supporting evidence I provided, SSDs (as hardware devices) are ideally suited for the type of data used by PFs.

And then you have to use this comment about being in the military for 24 years to defend my ability to have an opinion but not so I can express it? And if I did not quote that word for word from your previous message, you come back and accuse me of misquoting.
WRONG!!! It is not about misquoting or word for word. It is about you twisting the meaning and fabricating what was said. That is what you have repeatedly done multiple times. It is wrong, childish, and totally unprofessional!

You cannot post false information as a technical fact, then claim it is your opinion and that you have the right to express it. Nor can you claim someone said something after you twisted their words around into something they did not say.

So why do you think that it is best kept on the SSD boot drive? Well, you can say it is best to do so but I say no it is not. But only in MY situation.
I don't "think" it is best, I know it is best! And I know because I do my homework and research and verify and learn! Those are the facts, as spelled out in the supporting FAQ link I provided. It is not my opinion, just a technical fact that for the best page file performance, put it on an SSD.

Could there be exceptions? Sure! There are exceptions to every rule (except maybe that one). But exceptions do NOT make the rule. Nor do they apply to the vast majority of users.

I am sorry tteksystems, but YOU ARE NOT EVEN USING COMMON SENSE!!!! :( Think about it for just a second and PLEASE consider the following facts (not my opinions, but facts):

Fact: Overall Page file performance is virtually 100% dependent on (and limited by) the performance capability of the drive the PF is stored on.

Fact: Hard drives have consistently (for decades!!!) been the major bottleneck in data transfer bandwidth within the computer. Why? Because they are mechanical devices and mechanics move slower than electrons flow through circuits (note: I said "within the computer" because network bandwidth may be worse).

Fact: The slowest SSD is many times faster than the fastest HD.​

OF COURSE, if your SSD is small to begin with and running out of room, moving the PF to a HD is a viable solution. I have never said otherwise. But note your typical PF is only a few gigabytes in size. If you are that low on disk space, that freeing up a few Gb of disk space matters, you have other, more serious issues, and - here we go again - you will either need to free up space, or buy more.

That said, if you don't care about maximizing your computer's performance, why buy an SSD in the first place?

Now, if you want to discuss the technical facts as they apply to the vast majority of users and not an issue that applies "only in MY situation", then let's discuss. If you want to discuss your unique "only in YOUR situation", then I recommend you open your own thread instead of hijacking someone else's. :(

Otherwise, I am done dealing with your puerile crying about feelings being hurt. If you are going to present a technical post in a technical forum frequented by highly technical and highly regarded (and globally recognized) professionals, you better be prepared for a critical technical "peer review" of your posts, and check your emotions at the sign-in page. And if you want to avoid another situation like this in the future, do your homework first to ensure you know the true facts before posting.

*******

@Techno Venus - probably way too late now since this issue was dredged up from over 5 months ago, but in reference to Indexing and bogging down systems, as I noted before, Indexing on a new system can take a long time. And on modern operating systems and in particular, W8, the Indexing service has been greatly improved to minimize impacting performance while the user is not idle. But, the process is not perfect. And with potentially several 100 thousand files in 10s of thousands of folders, it can take a long time - especially as a background process.

But once complete, indexing only has to deal with changed or new files and that is simple, and quick.

The problem is, getting the initial indexing to finish - but depending on what your computer does when you step away from it can greatly impact indexing. What I and others have done is change our sleep settings so the computer does not go sleep when we walk away so Indexing keeps crunching through the night. In a day or too, even full monster size disks can be fully indexed. Once indexing is complete, sleep mode settings can be restored.

Like most of the extra tools integrated into Windows 8, they have been greatly improved from previous versions of Windows, though they are still "basic" tools with no flair or fancy features or enhancements. But the reality is a "basic" tool is all most users need. This includes the Search feature in Windows. But some users want more and fortunately, Windows allows us to add 3rd party apps that are more than basic tools. So if a user has a need for frequent searching of their hard drives, adding a 3rd party drive search tool may be desirable and in that case, Indexing probably should be disabled.

BUT - if disk space is a problem, I see no reason to download and install a 3rd party app that takes up more space.

*******

satrow said:
Even Mark Russinovich has changed his tune on page file sizing some 3 times, maybe more, and that's just where he was trying to generalise - for the majority of users.
Right! But Mark also says to just let Windows manage it if you are not going to take the time to properly analyze AND UNDERSTAND your virtual memory requirements.

I've changed the page file sizes some 4 times on my main PC since #5 here, simply because my workload is frequently changing
Which is exactly why I recommend users let Windows manage it - especially with modern versions of Windows - even among experts. For one, Microsoft has had more than 20 years to tweak the process. But more importantly to my (and your) point is things change. You can analyze your virtual memory and set a "fixed" page file size and that may be perfect - today. But tomorrow, you may install or uninstall a program, update Windows, or otherwise change your computer or your computing habits, changing the optimal settings for your PF. But unless you regularly go back in and re-analyze your requirements, you can easily, and users often do end up with a PF setting that is not optimum.

Modern Windows takes care of that for us and does a darn good job of it too.

*******

Personal comment: When it comes to buying or building a new computer, or upgrading an old computer with a new motherboard, I see SSDs in the same light as Windows 8. Windows 7 is already nearly 5 years old! W8 is inherently more secure, and offers better performance - ESPECIALLY when connected to today's hardware, which includes SSDs. So why bottleneck your hardware with a 5 year old OS? Sure the W8 UI can be a roadblock for some (I don't like, or use it!) but with programs like Start8, it is extremely simple and inexpensive to make W8 look, feel and behave like W7, only a little quicker.

Hard Drive technologies are more than 60 years old!. There are many moving parts inside an HD with two motors, 2 or 3 or more actuator arms (depending on the number of stacked platters) and supporting infrastructure. There are no moving parts in a SSD. SSDs today many time faster than HDs. SSDs today are even 3 or 4 times faster than SSDs of just a couple years ago and no longer suffer from a limiting number of writes.

If you are looking for the most budget oriented computer, then go HD and understand you are bottlenecking performance. But if you want a modern computer, one that you can expect will last you many years into the future without any mechanical breakdowns, then common sense says if you want to take full advantage of all your hardware's capabilities, go SSD and W8.

***

240Gb SATA III SSD for $90 after $20 Rebate!I paid 4 times that for my first 20Mb (yes, Mb) HD!
 
Last edited:
satrow said:
Even Mark Russinovich has changed his tune on page file sizing some 3 times, maybe more, and that's just where he was trying to generalise - for the majority of users.
Right! But Mark also says to just let Windows manage it if you are not going to take the time to properly analyze AND UNDERSTAND your virtual memory requirements.

I've changed the page file sizes some 4 times on my main PC since #5 here, simply because my workload is frequently changing
Which is exactly why I recommend users let Windows manage it - especially with modern versions of Windows - even among experts. For one, Microsoft has had more than 20 years to tweak the process. But more importantly to my (and your) point is things change. You can analyze your virtual memory and set a "fixed" page file size and that may be perfect - today. But tomorrow, you may install or uninstall a program, update Windows, or otherwise change your computer or your computing habits, changing the optimal settings for your PF. But unless you regularly go back in and re-analyze your requirements, you can easily, and users often do end up with a PF setting that is not optimum.

Modern Windows takes care of that for us and does a darn good job of it too.
Bill, that doesn't take into account any real world usage for machines with multiple drives, increasing disk I/O on the System drive when there are alternatives with usually lower base I/O levels might not be the best plan.

My System drive is an mSATA SSD with read/write speeds of 265/251 MB/s (most mSATA motherboard connections are SATA 2), my secondary SSD has read/write speeds of 507/250 MB/s and my 2.5" HDD is around 90MB read and write.

I have paging files spread across all 3 drives (the only 'fixed' size PF is on the System drive, which has the highest I/O anyway), when the SSD PFs become busy/full, Windows will use the HDD's PF. Until that point, ie. for my normal usage, I suggest my setup is better than Windows' default.

When the HDD PF does come into use, I can hear it, giving me an audible warning that 'something' is close to hitting the limits on at least one of the SSDs.

Currently on 8.5 days up time here and the Currently Allocated PF is still at the minimum level, 1.5GB (of 2.4), even though there have been a number of periods when the used memory has been over the 6.5GB (of 8) mark.
 
Sorry satrow, I will come back in a bit after dinner (though it could be tomorrow) to reply to you, if you don't mind. But first...

@tteksystems - As I sit here with my martini, I think we both started off on the wrong foot. But I blew it because before anything else, I should have welcomed you to Sysnative. It really is warm and inviting place where you can share what you know and definitely learn something new along the way. So I should have said, "Welcome to Sysnative", and I apologize to you for not doing so first. I assure you, I am not on the Welcoming Committee and I am of no reflection to anyone on the rest of the staff or regulars here.

For my [okay, flimsy] "excuse", I was formally trained (brainwashed?) that anything that plugs into the wall can kill. I was trained (in the AF and for my degree) in "technical writing" and editing that stressed facts and to the point style, just to avoid confusion or misinterpretation. I worked, was trained, trained subordinates, supervised all in electronics repair facilities where exposed deadly voltages were an every day thing. No room for horseplay, no room for misunderstanding, no room for emotions - NOT because it was a military environment, but because that is the right and safe (which tend to go hand in hand) thing to do where any misstep can cause further damage, or worse. Probably like operating rooms and ERs - organized chaos. Or at least it was my job to keep it organized - so "my troops" did not zap themselves, zap the equipment they were repairing. Or worse, take down the mission and get the Colonel on my a$$. Or worse yet, get blood on my shop floor, or maybe killed (you can't image the paperwork! ;)).

So as a grumpy ol' Master Sergeant, who spent over 4 decades providing support for IS/IT, I understand I may "bark out" my response. But I assure you, it is nothing personal, only technical - my goal is ONLY to ensure the average reader (as in "normal user") has all the true facts to make an "informed decision" based on "their" situation. And frankly, that is how I feel every tech support forum should work - at least until a specific environment/scenario is fully defined.

So again, no offense, or anything personal meant. My goal is only to ensure readers have the facts so they can make informed decisions.

Anyway, I think we can reboot this. And since I (for the moment) still have a minute amount of pull around here, it will not be hard. I recommend you revisit your first post and first, identify your audience. If you think what you post applies to most "normal" computer users, then address it to them. If you think it is an advanced feature for enthusiast, the IT professional, or to those out in the extremes of the "normal computer user", then address it them.

If you are wanting to relay your experiences with a specific problem you encountered with your "unique" system, and how your remedied it, then, please, share your story. Others may learn from it. And BTW, you recently said this scenario applies to "only ME". With nearly 1.5 billion Windows users out there, no way is there "only ME". We all have different motherboards, drivers, monitors, browsers, sound cards, ISPs, graphics, solutions - even versions of Windows, but there are certainly others who can benefit from your input - and that's what forums are about.

But please, if you are talking about changing OS defaults, you MUST, absolutely MUST identify the OS version this applies too. And please remember that EVERYTHING you thought you new about virtual memory (which includes RAM, some caches, and the PF) has been greatly improved in W7 from Vista, and especially from XP. And there have been further improvements with W8.

And note part of that is because the hardware industry is rapidly advancing technologies on their own. In fact hardware advances MUCH FASTER than software revisions can keep up! 64-bit is the perfect example. The AMD64 (after leapfrogging past the complacent Intel sitting on their Laurels) came out years, MANY YEARS before the software industry (except MS with 64-bit XP Pro).

If you are going to express something as a fact, please do as I do and verify with my friend Bing Google first. And if it is counter to common belief or defaults, or to a previous post, please provide some collaborating evidence or link, or very sound rational.

Then post anew, either here or in a new thread. It will not be hard to then remove all these unnecessary posts in between. But again, this site is full of IT experts with expertise in many areas. So make sure your "facts" are correct and be prepared to defend them WITHOUT getting emotionally offended, or offensive. Technical criticism is not, or at least is not meant to be personal.

So, again, sorry for my lousy "welcome".
 
Likewise, there are times when I lock my CPU maximum frequency down to the minimum for several days at a time because there's no heavy number crunching that needs to be done.

Do you mean that you usually over-clock your system or are you referring to something else?
 
Likewise, there are times when I lock my CPU maximum frequency down to the minimum for several days at a time because there's no heavy number crunching that needs to be done.

Do you mean that you usually over-clock your system or are you referring to something else?

In his case that would be undervolting as opposed to overclocking as he's bringing his CPU clock below the default but also at a # that still runs.
 
Likewise, there are times when I lock my CPU maximum frequency down to the minimum for several days at a time because there's no heavy number crunching that needs to be done.

Do you mean that you usually over-clock your system or are you referring to something else?
No, I'm currently stock @3.3/3.7 turbo but I do sometimes push it to 3.4/3.85 if I'm running something very CPU dependent; I lock it down to 1.6 GHZ when I hit a quiet period - saves a few pennies, keeps the room a little cooler, stops the CPU fan from spinning up and down and distracting me ...

The only thing actually undervolted is my RAM, regardless of CPU speed, and that's only @1.25V, down from 1.28 stock, on tighter than stock timings but stock speed.
 
Last edited:
satrow said:
Bill, that doesn't take into account any real world usage for machines with multiple drives, increasing disk I/O on the System drive when there are alternatives with usually lower base I/O levels might not be the best plan.
In "managed" computer systems, I totally agree. That is, where there is a user with that level of expertise and knowledge of the pros and cons, and has the desire (if an enthusiast) or the responsibility (as part of their job) to stay on top of it to make the necessary "tweaks" in a timely manner as changing demands require, then I say go for it! But for the vast majority of users, they don't care about such things, or even know about such things. They just want it to work. And that is how it should be.

And with Windows 7 and more so in 8, Windows is fully capable of managing single, or multiple page files - and do so dynamically (no need to reboot) - which you can't do with a fixed setup.

most mSATA motherboard connections are SATA 2
Ummm, no, not anymore. Perhaps if talking about motherboards already in use, but anyone buying a new motherboard or new computer today should be looking for the latest versions for the best future proofing, be it 6 Gb/s SATA, USB 3.0, and hopefully HDMI 2.0 too (or at least 1.4). And you don't have to pay an arm and leg for the latest either - especially with motherboards. As long as the motherboard of choice supports the latest I/O, that's all the vast majority of users need, and they don't have to spend a fortune to get it with most costing well under $100 (though I would avoid the very cheap entry-level models). I note according to Newegg, out of 178 µATX Intel based motherboards they list, 137 come with 6Gb/s SATA (SATA III), and USB 3.0 too. I suspect it is similar for AMD boards.

I've been building my own systems since the early 90s and up until now, including with my [now demoted] main W7 system, I had similar set ups to you and manually managed my PFs too, because I did a better job - well, with my XP systems anyway (I never migrated to Vista but that is where virtual memory management really started to improve). But since XP, Microsoft's stable of PhDs, and super programmers, CompSci pros and racks of super computers have not been sitting still. Windows 7 knows how to manage virtual memory very well, and W8 does an even better job yet!!! So I let it - with no regrets. In fact, my life is easier now because I let W8 manage my page files.

I built this i7, 16Gb RAM machine for W8 (the first Windows OS built with SSDs in mind from the get-go). I have a Samsung 256Gb 840 Pro (540/520) as my boot (C) drive. It holds Windows 8.1 and all my program files are installed somewhere under c:\installed programs\. These include Office 2007 and Outlook 2010, Chrome, FF, Pale Moon, all my security stuff and I still have over 150Gb free - plenty of room for Windows to dynamically optimize the PF and a full complement of System Restore points too.

I have a large secondary harddrive with 64Mb buffer that is no slouch, but doesn't hold a candle the SSD. It holds copies of my 600+ music CDs. Plus that is where I initially download all my downloaded programs, and this HD houses my first level of backup files. Except for downloaded programs, all these files are static - they don't change or "run" and basically the downloaded program files run only once, to "install" the program on to the SSD.

In other words, for the most part, unless I am listening to one my ripped CDs, I am running 100% from the SSD almost 100% of the time. To the comment earlier that SSDs offer "NO advantages" to programs or files, well, that is simply, and blatantly obvious to not be true. I have a 50 page MS Word document with 110,000+ characters and 16,000 words that contains all my canned texts and links I use for my forum "work". I call that doc up multiple times a day by clicking a shortcut link to the doc from my Quicklaunch toolbar (hidden in W8, but something the Luddite in me cannot do without). It literally "pops-open" - that is, it takes less than 1 second for W8 to call up Word and open the document.

I note your slowest SSD is 3 times faster than your hard drive and the faster SSDs are 6 or more times faster.

satrow said:
I have paging files spread across all 3 drives (the only 'fixed' size PF is on the System drive, which has the highest I/O anyway), when the SSD PFs become busy/full, Windows will use the HDD's PF. Until that point, ie. for my normal usage, I suggest my setup is better than Windows' default.

When the HDD PF does come into use, I can hear it, giving me an audible warning that 'something' is close to hitting the limits on at least one of the SSDs.
Ummm, sorry satrow, but I am afraid that clearly tells me your manually configured virtual memory setup is not right! If it was, the PF on your boot drive would NEVER get full and be forced into a bottleneck (the HD's PF).

That "something" getting close to the limits is the PF on SSD screaming for more space! So, if that were my system, I absolutely would give it more space! And I would do it by letting W8 manage it, ensuring there was a nice chunk of free space available on the drive. And if not enough free space, then I go back to earlier advice and recommend you free up space by moving programs to a different drive, uninstalling unused programs, or by buying more SSD space - then let Windows manage it.

******

I know several HTPC (home theater PC) owners who underclock their systems to keep heat at bay and fans off. When you have $2,000, $10,000, $50,000 or more tied up in your home theater system, the last thing you want is to hear your HTPC fans rumbling along during some quiet movie passage. You don't want to hear your HD motors humming and clicking either - so more and more users are also going SSD for that reason too. For the PVR function, some use monster 5600RPM drives as they tend to be pretty quiet. But a couple I know just map to a networked drive in another room for saving/streaming recorded shows.
 
I don't use, or suggest others use, a fixed setup; my System SSD (the one with the highest base I/O and lowest speed) has a fixed PF, the secondary SSD (faster with lower I/O) has a flexible PF and the HDD's PF is also flexible.

Why do I even have a PF on the slow HDD? In part, so that I can find out how much PF space my usage requires: it's plain that I don't need the 12GB that Windows wants to set - on the drive that already has the highest I/O. 1.5-2GB is much closer to the mark and I currently have 1.4-2.4GB allocated, or ready to allocate, on the SSDs. It's also there a a fall back should I forget to exit some diagnostic/test software that might chew through the memory, or in case of a buggy software - I test a lot of software before it reaches Release stage.

When 'something' uses more resources than I anticipated, I need to track down the source and work out why. No, I've not heard my HDD work since before my last PF changes, it's not used any more than the minimum allocated 100MB since then.

If MS were to upgrade the Virtual Memory system so that we could (or Windows by default would) duplicate the PF across the different drives, that might become my preferred option as we've already been informed that Windows since Vista will read the PF data from the fastest available source.

I was only comment on the current situation: most mSATA motherboard connections are SATA 2; sure, in a year or two, that might change as more people upgrade their systems to Haswell+.
 
I don't use, or suggest others use, a fixed setup; my System SSD (the one with the highest base I/O and lowest speed) has a fixed PF, the secondary SSD (faster with lower I/O) has a flexible PF and the HDD's PF is also flexible.
Sorry - you just confused me. You said you don't use a fixed setup then said you have a fixed PF on your boot drive.

Why do you have a limiting fixed PF on the one drive (the boot drive) that really needs full access to all that is available? Are you low on free space with this drive? And what OS are you running?

I fail to see how limiting that space helps you decide how to track down the offender any easier. You don't need to run your VM into a brick wall to see what is using it.

I was only comment on the current situation: most mSATA motherboard connections are SATA 2; sure, in a year or two, that might change as more people upgrade their systems to Haswell+.
I think it is happening now - not in one or two years. After all, SATA III has been the current standard for over 5 years now!

I showed how Newegg sells many times more SATA III boards than 2. And even Dell and HP systems with µATX boards support SATA III. And Haswell has nothing to do with it. For one, that is an Intel CPU and AMD is still going strong and for another, CPUs don't care! They have nothing to do with SATA 2 or III. That is a chipset function and all the current crop support SATA III.

And again, the vast majority of users could care less the name of the line of CPUs. Most just care, if they care at all, that they have Intel or AMD, quad or dual, and the clock speed - and of course, cost.
 
And with Windows 7 and more so in 8, Windows is fully capable of managing single, or multiple page files - and do so dynamically (no need to reboot) - which you can't do with a fixed setup.
If the above is a definition of a fixed setup then I don't have one. I can allocate more PF space on the secondary SSD and/or the HDD dynamically, no need to reboot. (System specs are in the dropdown below my avatar.)

Getting Windows to manage multiple PFs requires manual intervention to create them, how well it 'manages' them is still open to interpretation, as far as I can tell.

It only needs a swapfile when RAM usage approaches 92%.

As the System SSD already has the highest base I/O and is the most likely to become the bottleneck, why should I increase the workload on it when I can switch some of that load over to the secondary SSD?

Limiting the amount of PF allocated allows me to detect any big memory leak quicker if I'm near the PC; with a System managed (or Windows' default) PF on the System SSD, I'd need to be constantly watching for popups.

mSATA, while related to SATA 1/2/3, isn't the same thing as the interface is different, it's only recently that there have been mSATA drives and motherboards with an mSATA interface that are capable of reaching SATA 3 speeds.

I used Haswell as a marker, an approximation of the availability period: prior to Haswell becoming available, I don't think there were both mSATA/SATA 3 drives and 'boards available to enable that speed, since then, they've begun to reach the market. With an adapter, however, it is possible to reach SATA 3 speeds with a fast mSATA drive via the standard SATA (3) motherboard interface, no need to upgrade the motherboard to mSATA 3.
 
If you are not letting Windows manage your PF, then it is fixed, or at least that is how I define it. With Windows managing, your PF will expand and contract as required, based on the demands put on the system. If you set limits, then you set "fixed" limits.
It only needs a swapfile when RAM usage approaches 92%.
Says what? Got a link? The fact of the matter is, RAM does not need to be near full for Windows to use the PF. It can and does stuff data in it even when there is lots of RAM left. For example, if you minimize MS Word and don't use it for bit, Windows may move that data out of fast RAM and stuff it in the page file. And that's fine because reading that data back in from the PF is still much quicker than finding and gathering up the file segments on the disk, re-loading those Word files and finally "executing" the program again - a process that takes up quite a bit of RAM and considerable CPU resources - at least for a couple seconds. That is why I am flabbergasted when I hear folks disabled the PF altogether - claiming they have enough RAM, they don't need a PF. That is not how virtual memory works and forcing the OS to only use RAM is not optimal. I fear there is this perception (misconception!) that using the PF is bad thing. It is not - even when the PF is on a HD.

mSATA, while related to SATA 1/2/3
Okay, my mistake. Sorry. Not sure where I got off track, but I thought you were talking about microATX (µATX) sized motherboards - hence my links to Newegg and µATX boards and my several comments about small µATX (and ITX) boards.

So forget what I said about that and sorry for the confusion.

That said, mSATA or miniSATA are NOT your typical interfaces used, except in small notebooks and tiny portables for which mSATA was created. So we are talking apples and oranges here, and definitely not what most users will encounter - at least not until the PC goes away and we all move to handhelds - which will happen when they can fit my two 22" monitors, full sized keyboard, mouse and THX surround sound speakers into my smartphone. ;)

why should I increase the workload on it when I can switch some of that load over to the secondary SSD?
I could care less about that. My issue all along is to put the PF on SSDs, because SSDs are ideally suited to house the PF. I personally don't care which SSD. Just as long as it is not on a sssllllooowww hard drive, unless SSD space is critically low. But note if you "move" the PF from the system drive, you may lose out on memory dumps that can help in troubleshooting.

Getting Windows to manage multiple PFs requires manual intervention to create them, how well it 'manages' them is still open to interpretation, as far as I can tell.
Yes, it requires manual intervention (two clicks, one time and it's done - so hardly a challenge, if you let Windows manage them). But multiple PFs is NOT normal! Nor is it normally required even with multiple drives. One page file on the system disk is all the vast majority of users need, regardless the number of disks in their system. In fact, I see no reason for multiple page files at all on a properly setup computer, unless you have more than one OS on the multiple drives. Or you are doing specialized troubleshooting as part of software development and testing - again not something normal users do.

We cannot let exceptions set the rule especially with the latest versions of Windows. What I am saying, satrow, is your setup (and your expertise in memory management ) is hardly typically. Kudos to you if you have the time to keep constant watch and you have mastered memory management. Most people don't.
Limiting the amount of PF allocated allows me to detect any big memory leak quicker if I'm near the PC; with a System managed (or Windows' default) PF on the System SSD, I'd need to be constantly watching for popups.
Huh? NO! What popups? Popups are bad. You don't want popups. And you won't get popups if Windows is managing your PF AND you have plenty of free space on your drive to allow Windows to operate freely in. A popup means you ALREADY have hit a critical low. That indicates VM is not setup properly! And I see no difference in you "being near the machine" vs sitting in front of it watching.

I understand if you are testing new code you want to see how it is utilizing memory, but there are programs for that. Putting a choke collar on the ENTIRE operating system to test one piece of software is NOT something any normal user will do. So your scenario is not typically and should not be applied to others unless they are as "abnormal" as you! ;)

FOR SURE, as an electronics technician for many years and a computer enthusiast and IT professional for nearly as long, and as a beta tester for several software developers, I have systems here that certainly not set up with default settings too. But when it comes to advising the crowd of computer users, it is a "do as I say, not as I do" situation. For example, I use CCleaner's Registry cleaner all the time, but that is not something I would recommend for all, or even most.

And for the record, I am NOT saying Windows can managed PFs better than ALL users. But I am saying it does better than the vast majority of users simply because the vast majority of users don't have the, or ANY expertise in virtual memory management. Nor to most users have the discipline to constantly monitor and adjust as necessary.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top