Page fault/Sec, cache fault, and Stack OverflowLatency are issues.
The counter pages are almost zero.Sometimes it goes up to 300 for a second.Over time, therage is about 10.
The cache faults are zero for 2-e seconds and then raise to about 10000 for 1-2 seconds.All the time, this is repeated.
We had a lot of string conversions from the data layer data reader.
We were caching a lot of the same strings in the asp.net cache.This is only used to cache the reference to a list.We changed the caching so that we only cache things that will be used on all machines in the.net cache, and not necessarily on the same server, which will free up GC.
If you're talking about page faults on asp.net, you should look at the server logs and see what's going on.There should be a lot of.net errors.
This could be normal if you are talking about memory page faults.A memory page fault is a signal in the hardware to shift data from virtual memory to physical memory.The page fault can be found at http://en.wikipedia.org.
Increasing the amount of physical RAM in the machine is the best way to lower Memory page faults.
The basics of page-faults can be found in the archives at http://blogs.technet.com/b/Askperf.