re:
!> The rapid memory growth is happening on the production server, so how
!> will I attach Visual Studio.NET to debug it while scores of users are on it?

You shouldn't be debugging on the production server, anyway.

What is stopping you from debugging on your development server ?

Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================

Sorry for misunderstanding you, David. Are you sure that you can't reproduce
the problem even on a small scale on the development server? If so, as well
as adding performance counters, you may be able to narrow down the possible
culprits. First, when you say "rapid memory growth" are you referring to
simple memory usage increase, or a memory leak, that is, memory which
accumulates until the app recycles? If it's a simple matter of rapid memory
growth that levels off at a certain point, this is most probably due to the
amount of traffic using the web application. Garbage collection will allow
memory to accumulate up to a point as it manages the memory, as it often
reuses de-referenced object code. If it's a memory leak, it may be caused by
improper use of COM interop, or memory fragmentation, so you can also look
for possible candidates in that area.