Windows 7 alone using 36gb

jwells10 · 13 Aug 2010

karlsnooks said:

jeweils,

This is Win 7 and not XP. Microsoft has learned much. Win 7 is a very finished product. You can only make things worse by tinkering with it.

Enjoy a fine and polished operating system.

All of the tweak and other products of that ilk and advice of that type can only do you harm.

Add-on products that the most of us use are CCleaner and

A big friend is the key combo WIN + F! for the windows help system and just type your question into the search box. Here is another area that has improved immensely over XP.

I use CCleaner and Microsoft Security Essentials , and the reason I set it to 2048MB is because i only have 1GB or RAM
haha yes i know windows 7 is a very improved product i fell in love with it ever since the beta but my tinkering with a page file has fixed all my problems

karlsnooks · 13 Aug 2010

What I am saying is that your original tinkering was the source of this problem.

Have a nice day.

jwells10 · 13 Aug 2010

cluberti said:

How much RAM do you have in this system? If you've got 4GB or more, you can probably set the paging file to 512MB or less, or even disable it depending on what you do with your PC regularly.

Haha I use my Computer for AIM,Gaming and dabbling in the arts of cracking and Programming (not maliciously of course :3 )

jwells10 · 13 Aug 2010

karlsnooks said:

What I am saying is that your original tinkering was the source of this problem.

Have a nice day.

I dident tinker with it in the first place, i was having that problem after a clean install, my tinkering only fixed the problem : )

**cluberti** · 14 Aug 2010

karlsnooks said:

cluberti,

The XP days are gone. Win 7 is without equal at selecting the optimal pagefile for your system.

You can run with no PageFile but you will notice a different performance, regardless of the amount of ram.

Indeed it does a decent job of creating a paging file based on the algorithms of paging=1.5x RAM at 1GB or less, paging=1x RAM at 2GB or more. However, the memory manager still has bias where if you provide it more paging file space, it'll use it more frequently. Yes, it is better than XP at keeping more data in RAM thanks to more efficient memory manager code, but that doesn't mean that code is entirely "better" or "fixed" - there's really no need to incur the overhead for paging to disk when it isn't necessary, and there are data collector sets one can use to figure out whether or not you're using a paging file or not under regular load, but that's a different thread altogether.

If this is something you want to chat about offline, let me know and we can do that. There are a whole host of things I would rather not post here as well so as not to sidetrack and hijack the thread further.

**cluberti** · 14 Aug 2010

jwells10 said:

karlsnooks said:

What I am saying is that your original tinkering was the source of this problem.

Have a nice day.

I dident tinker with it in the first place, i was having that problem after a clean install, my tinkering only fixed the problem : )

You could very well have an application or driver making requests to reserve large amounts of virtual address space, but not committing them. Since (on Windows, anyway) any reservation of VA that isn't strictly memory-mapped must have a page in the paging file for every page in RAM, making large reservations can cause Windows to inaccurately increase the paging file to try and make sure that if those reservations are ever called on, it has the paging file to back it BEFORE then (so as not to take a huge perf hit if it has to back those reservations - it's much quicker to increase it in small amounts in a lazy fashion rather than attempt to extend the paging file all at once). I've seen it a few times where this happens due to buggy drivers (I've personally never seen user-land software do it, but I suppose it's possible), and manually fixing the paging file will "solve" it.

jwells10 · 14 Aug 2010

cluberti said:

jwells10 said:

karlsnooks said:

What I am saying is that your original tinkering was the source of this problem.

Have a nice day.

I dident tinker with it in the first place, i was having that problem after a clean install, my tinkering only fixed the problem : )

You could very well have an application or driver making requests to reserve large amounts of virtual address space, but not committing them. Since (on Windows, anyway) any reservation of VA that isn't strictly memory-mapped must have a page in the paging file for every page in RAM, making large reservations can cause Windows to inaccurately increase the paging file to try and make sure that if those reservations are ever called on, it has the paging file to back it BEFORE then (so as not to take a huge perf hit if it has to back those reservations - it's much quicker to increase it in small amounts in a lazy fashion rather than attempt to extend the paging file all at once). I've seen it a few times where this happens due to buggy drivers (I've personally never seen user-land software do it, but I suppose it's possible), and manually fixing the paging file will "solve" it.

I looked and it dosent seem that a driver was responsible, from looking at memory logs and such ive found that the most likely culprits were Firefox and AIM, they both had an abnormally large memory load at the time

**cluberti** · 14 Aug 2010

Like I said, anything's possible - I've learned over the years never to rule out anything until you can actually test and rule it out as a potential suspect

.

jwells10 · 14 Aug 2010

cluberti said:

Like I said, anything's possible - I've learned over the years never to rule out anything until you can actually test and rule it out as a potential suspect

.

Haha yea : )