Computer Speed Trick
GhostfaceKillah
Join Date: 2002-10-05 Member: 1438Members
Join Date: 2002-10-05 Member: 1438Members
in Off-Topic
<div class="IPBDescription">very fast</div> For those of you that love the biggest and fastest computers out there here is a little trick i have learned and will be using/trying soon.
Virtual memory is like ram that you computer uses but on your hard drive.
Now imagine that your computer wishes to read off the HD and read off of the VM, it cant do both at once.
So this can slow your computer performance quite a bit. This is what i advise to you. Get another HD small like 2gb and set your VM to use that drive and give it a value that is about 150% of your ram(max and min)
It is important that you have your main HD on the primary IDE and the VM on the secondary IDE. Both HDs should be on the master side of each IDE.
This information came to me from another forum, so I dont take the credit.
I havn't tried this yet, but ill; post back when I do.
Virtual memory is like ram that you computer uses but on your hard drive.
Now imagine that your computer wishes to read off the HD and read off of the VM, it cant do both at once.
So this can slow your computer performance quite a bit. This is what i advise to you. Get another HD small like 2gb and set your VM to use that drive and give it a value that is about 150% of your ram(max and min)
It is important that you have your main HD on the primary IDE and the VM on the secondary IDE. Both HDs should be on the master side of each IDE.
This information came to me from another forum, so I dont take the credit.
I havn't tried this yet, but ill; post back when I do.
Comments
Nice sig, BTW.
MonsE really knows what he's talking about. I haven't tried all of these tricks; "disable paging out the NT executive" was good enough for me to notice a performance increase.
Be warned though. With some machines, NOT running the VM swapfile on the primary drive can make BAD things happen, such as refusing to load the OS on MS-OSen. Set it up when you first build the machine so you don't risk losing access to your data, and you're golden. Recovering from a VM location error is significantly more complicated than the initial shuffle of the swapfile to the secondary drive.
And yes, set it to a static size. Slight boost, and you don't 'lose' HDD space unexpectedly.
Anyway, THE BEST WAY OF GETTING A FAST COMPUTER is:
- Get some hackers
- Get some bad guys
- Get some black clothes
- Go to Japan
- Steal the supercomputer that's simulating the world
- Get an aircraft hangar (the big one!) <!--emo&:D--><img src='http://www.unknownworlds.com/forums/html/emoticons/biggrin.gif' border='0' style='vertical-align:middle' alt='biggrin.gif'><!--endemo-->
Now imagine that your computer wishes to read off the HD and read off of the VM, it cant do both at once. <!--QuoteEnd--> </td></tr></table><span class='postcolor'> <!--QuoteEEnd-->
Since I teach these things I have to comment.
You have "virtual memory" in your RAM and cache as well. It's simply a way of addressing your memory and not a type of memory. If you didn't have virtual memory then every program would be forced to be at a specific place in the memory or else most jumps would go to /dev/null/ <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->
Virtual memory gives the programs an address space where they can run their code and store data without having to think about where in the pysical memory they are really placed. The OS job is also to make sure that no programs can write to each others memory space by misstake.
Virtual memory and swap space is not the same thing. Swap is simply something that virtual memory use when it runs out of RAM.
I'll take two.