Sun 8th March 2009.
Vista 64 bit is running sweet as a nut, allbeit a nut with proper sound card... 4gig of ram installed....
Page File goes off now, cos my Raptor cranks it's arse to dust every time I boot up at the mo.
Sun 8th March 2009.
Vista 64 bit is running sweet as a nut, allbeit a nut with proper sound card... 4gig of ram installed....
Page File goes off now, cos my Raptor cranks it's arse to dust every time I boot up at the mo.
Originally Posted by Advice Trinity by Knoxville
it's off, and after a reboot, the raptor is still grinding it's arse to pieces for 30 seconds.
weird.
Originally Posted by Advice Trinity by Knoxville
I have always thought that running without a page file was a bad idea, when I tried running without for a while I constantly got programs moaning about not having one, other than that had no real performance increase or decrease.
I have however seen my performance increase through spreading my pf over all 3 of my drives (1gb each) things go much smoother now.
*̡͌l̡*̡̡ ̴̡ı̴̴̡ ̡̡͡|̲̲̲͡͡͡ ̲▫̲͡ ̲̲̲͡͡π̲̲͡͡ ̲̲͡▫̲̲͡͡ ̲|̡̡̡ ̡ ̴̡ı̴̡̡ *̡͌l̡*
Originally Posted by Winston Churchill
One way to check is to go to the Administrative Tools, then Reliability and Performance Monitor. You can check what is utilizing the Disk at that location.
It was quite a time ago, but I think running without resulted in a fair bit more memory being used, and single digit percent performance increase in benches, whereas spliting it up over 3 drives gets pretty much the same performance (haven't compared benches like this as I don't remember the original figures, plus I have oc'ed the gfx card and found a couple of hundred mhz in the processor since then so wouldn't be a like for like comparison) but my system will never pause for a second or so when getting something from the pf anymore, not that it did that much anyway, but now it has never done it.
*̡͌l̡*̡̡ ̴̡ı̴̴̡ ̡̡͡|̲̲̲͡͡͡ ̲▫̲͡ ̲̲̲͡͡π̲̲͡͡ ̲̲͡▫̲̲͡͡ ̲|̡̡̡ ̡ ̴̡ı̴̡̡ *̡͌l̡*
Originally Posted by Winston Churchill
I think prefetch is to blame for all the read/writes. After using 3dmark recently, I've noticed Vista is reading the entire 1.2GB 3dmark.dat file after it boots up. I'm currently testing with no pagefile and can't see anything being placed into memory. After five minutes I'm now down to virtually 0% HD access tho.
@ Zak33
Turn off Vista’s search indexing:
1. Start › Indexing options › modify › show all locations › double click users in summary of selected locations › uncheck users directory › double click start menu in the summary of selected locations › uncheck start menu directory › ok
2. Start › system › services › windows search › disable › restart
3. Start › computer › right click c drive › properties › untick Index this drive for faster searching
Disable system restore
Start › backup & restore center › Create a restore point or change settings › turn system restore off
Enable advanced performance for Sata HDD
Start › device manager › disk drives › double click › policies tab › enable advanced performance
Disable hibernation
Hibernation cost you approx 1 GB of your hard drive space, here is how to get it back:
Start › cmd › type: powercfg -h off › enter
Turn off Remote Differential Compression
Control panel › select: programs › turn windows features on or off › uncheck remote differential compression › ok
Disable unneeded start-up programs from loading
Start › msconfig / system configuration › services
Why would you expect less HDD activity on clean booting, after only disabling the pagefile?Originally Posted by Zak33
The activity relating to the pagefile during startup would be it being checked to see if it contains a memory dump from a bugcheck, resizing if its current size is greater than the mininum size configured, and then as a result of hard page faults caused by a shortage of physical pages.
On a system with 4GB RAM there shouldn't be any issue with a shortage of physical pages, so that would leave pagefile activity only as specific API calls or ageing (pages on the standby or modified lists getting hard faulted to the page file) - not something I would expect to be occurring in the first few minutes of the OS's uptime.
Suspend-to-RAM rather than shutdown and you should have a lot less HDD activity in general, as you won't be starting with an empty system cache or doing system initialization routines on resume.
~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3
There are currently 1 users browsing this thread. (0 members and 1 guests)