
UNSOLVED
High peak "Commit Charge" immediately after boot-up
Hi
I notice that, immediately after booting up my Precision 390, the peak "Commit Charge" in Windows Task Manager always exceeds 646900K, with no applications running. At this stage, the total "Commit Charge" is relatively low, typically below 135000K.
My computer works properly, but I wonder if other Precision users have come across a similar high peak "Commit Charge" phenomenon immediately after boot-up.
My Precision 390 uses the E6300 and 1GB RAM, with the pagefile set at 1024MB.
I notice that, immediately after booting up my Precision 390, the peak "Commit Charge" in Windows Task Manager always exceeds 646900K, with no applications running. At this stage, the total "Commit Charge" is relatively low, typically below 135000K.
My computer works properly, but I wonder if other Precision users have come across a similar high peak "Commit Charge" phenomenon immediately after boot-up.
My Precision 390 uses the E6300 and 1GB RAM, with the pagefile set at 1024MB.
Responses (2)
Solutions (0)
- Thanks, again, Davor, for a clear and detailed reply.
I appreciate that the peak refers to the highest value usage since boot-up, not the current value, but am puzzled as to why the peak is so high immediately after starting the computer.
Your Precision 390 appears to have a peak "Commit Charge" in excess of 650000K after boot-up. As you suggested, maybe Windows needs those memory resources to set the page file at boot time.
A little strange... :)

Davor Buvinic
12 Posts
383
0
Posted October 3rd, 2006 15:00
Maybe Windows needs those memory resources to set the page file at boot time.
My Precision 390 (2G RAM):
Total: 243416 kB
Limit: 4032616 kB
Peak: 652688 kB
I see similar values on a Precision 830 server (1G RAM, Windows Server 2003 R2)
On my Thinkpad z60t (1G RAM), the peak after boot is 304236 kB. On my old desktop (Athlon XP 2600+, 512 MB) is 224720 kB. On both systems the page file is smaller than on the P390 and P830.
- Davor