I have a server running a few different sites. We're seeing some performance and memory issues.
When I go to Worker Processes I see one of the sites with a Virtual Bytes count of 5 GB. The private bytes is a more reasonable 800 MB. The server is x64 with 8GB of memory and IIS 7.
Is it a problem that the virtual bytes count is so high, or is that a red herring? If the virtual bytes count is high, does that mean it's storing memory in the paging file which could be causing thrashing? Or does the application pool simply create a big chunk of virtual memory on Windows x64 and it doesn't affect other processes or get written to the paging file?