tac603 Posted November 18, 2007 Share Posted November 18, 2007 Hello all,I recently purchased an Acer Aspire 4720 laptop. It came with Vista and I managed to format and install XP on it after several attempts to slipstream SATA drivers into the installation cd. Now everytime I restart my XP, I noticed the Peak value in Task Manager --> Performance tab stays the same even after I restart / reboot. Can someone kindly help me out with this issue? Thank you in advance. Link to comment Share on other sites More sharing options...
Idontwantspam Posted November 18, 2007 Share Posted November 18, 2007 Maybe it always is the same? I'm not really sure... The peak might be the all-time-ever peak, or it could be for that boot. I don't know. Link to comment Share on other sites More sharing options...
tac603 Posted November 18, 2007 Author Share Posted November 18, 2007 Hi Idontwantspam, thanx for the reply. The laptop is a Core 2 Duo Centrino, and in fact my first ever system running a Core 2 duo, so I'm not sure if that's normal. On my old desktop, 2.6Ghz single core with 512 mb or RAM, and a few start up programs like antivirus etc, the Peak value is on average 200,000 upon every startup.. but on the laptop, the value stays the same, at 670,304.I have also set 1000mb for both min and max for the pagefile on both my desktop and laptop. Not sure if this has any affect on anything though. Link to comment Share on other sites More sharing options...
Idontwantspam Posted November 18, 2007 Share Posted November 18, 2007 On my dell laptop with a Core Duo (not a core 2 duo) Peak Commit Charge stays at 621864 pretty much constantly. I don't think you have anything wrong. But I could be mistaken about that... Link to comment Share on other sites More sharing options...
tac603 Posted November 18, 2007 Author Share Posted November 18, 2007 Hi again, appreciate your reply... I've just rebooted the system, the Peak value now is 671,568. I guess things are ok for now. Thank you sir. Link to comment Share on other sites More sharing options...
cluberti Posted November 19, 2007 Share Posted November 19, 2007 The commit charge is the peak amount of RAM and pagefile space that has ever been in use since boot (obviously the current numbers reflect approximately the current commit). Having a high peak value just means you had a lot of virtual address space in the kernel and running apps that were committed to either RAM or pagefile. For it to be similar every boot is actually pretty normal, honestly. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now