Windows 2003 Paged Pool issues

245 pts.
Tags:
Windows Server 2003
I have a large file system (2TB, 80 million files) that constantly runs terrible after it's paged pool hits 300MB.....In my case rather quickly. It appears the memory manager cannot trim memory fast enough no matter what I tell the registry. I can't seem to find any app leaks either. If have tried the Memory management settings in the registry. Any suggestions on how to deal with this rather than reboot? Anybody else see this happen a lot? -Joel

Answer Wiki

Thanks. We'll let you know when a new response is added.

I’ve seen this with a site I worked on that <i>had</i> a windows file server that contained uploaded images for a recently large cartoon movie that came out over the summer (any one remember the “stupid donuts” videos on YouTube?) (This was on a Quad Quad Core AMD 64 processor with 16G of RAM and 100G of drive space on a fiber attached SAN, all the system did was file shares.)

This was because we had this number of files in a directory. Unfortunately, to resolve the issue we moved the shared information to a SMB share on a linux system. Mainly becasue I’ve seen several instances where (no matter what tuning you make) windowss doesn’t handle tons of files in a filesystem well. (This coming from a Windows guy).

Any chance the filesystem can be cleaned up or moved into a DFS file share?

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Buddyfarr
    what are the server specs on this system?
    6,850 pointsBadges:
    report
  • Denny Cherry
    I agree, we'll need to know more about the system. How much RAM? x86 or x64? Can you define "constantly runs terrible"?
    66,010 pointsBadges:
    report
  • EastCoastGuy
    X86 4GB of Ram, dual core 4GHZ Xeon's. Win 2003 Ent Edition. We use it to archive mail. Once the memory manager hits 300MB (after 3 days of work) It starts crawling when read/writing data. Eventually RPC hangs. I tried telling memory manager to free up more memory at 60/50/40% but that didn't seem to help. Solution has been to reboot. And frequently.....
    245 pointsBadges:
    report
  • Jerry Lees
    What do you mean by memory manager? Are you talking about a .net memory recycle of the application (i.e. web.config or the like) or are you talking about the task manager application?
    5,335 pointsBadges:
    report
  • EastCoastGuy
    Memory manager is what windows uses to trim allocated paged pool memory in order for the OS to survive. You can have 2GB for free physical memory but if you hit the paged pool limit your OS starts hanging. See: http://support.microsoft.com/kb/q312362/
    245 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following