Hi!

task manager's "memory usage" should be taken with care. it is actually the
working set of the process, which represents amount of physical memory
available to the process at a runtime, but it doesn't mean it is used by the
process.

In .net, this memory is not trimmed to it's actual size until garbage
collection occurs.
You can initiate that manually by calling GC.Collect();, but it is not
recommended or
necessary.

once when another process requests for some memory, windows trim the
process' working set to it's actual size. You can try that by observing any
application's
"memory usage" before and after you minimize it (e.g. MS Outlook). You'll
see that it
reduces when minimized.

You can also implement that in your app by calling kernel32.dll's
SetProcessWorkingSetSize with min working set size and max working set size
parameters set to -1
But it is not necessary.

task manager's "VM size" (you'll have to add that column if you don't see
it) represents
process "private bytes", which means absolute number of bytes occupied by
the
process - this is where you should focus your search. This is important,
because once
this counter reaches your pagefile size (minus amount of memory occupied by
other running apps)
you will start getting OutOfMemory exceptions.

What you really wanna try is checking your code to see if you have any
non-disposed
objects adding up in your code.

That is - of course - if you have the code of the web-service /
web-application.