views:

1945

answers:

4
+4  Q: 

Memory usage in C#

I have a program that uses threads in C#. Is there a way to know programmatically the memory usage of the application? I want to limit the spawning of threads to say 10 megabytes of memory, how would I do that?

+12  A: 

If you want the memory of the entire running process and not on a per thread basis, how about:

// get the current process
Process currentProcess = System.Diagnostics.Process.GetCurrentProcess();

// get the physical mem usage
long totalBytesOfMemoryUsed = currentProcess.WorkingSet64;

There's a whole host of other process memory properties besides WorkingSet64 check out the "memory related" ones at the following link for the one that best suit

http://msdn.microsoft.com/en-us/library/system.diagnostics.process_properties.aspx

porkchop
+1  A: 

I'm with Will and Steve, don't do this unless you REALLY have to do it . . . that said . . .

if you really need to do it you can use the .Net Hosting APIs they're there so apps like SQL Server can host the .net framework within the application.

It gives you control over memory management etc, I've read the article but never used the API's, they're on my to-do list for some night when I'm bored and none of my other "fun" projects feel like fun that week :)

Hope this helps.

Binary Worrier
+1  A: 

You don't measure the number of threads in memory usage. Rather, take into account the number of "processors" (SMP / Multi-Cores / Hyper-Threading) to decide how many threads should run in parallel. Or use the ThreadPool, which is sized automatically to achieve a good thread-to-CPU ratio.

Lucero
Mhmm... you are generalising.What if thread can use unpredictable amount of memory ?
majkinetor
If the amount is unpredictable, you'll only know that you've run into trouble when the thread is already running. Therefore, if you are processing data which may lead to heavy memory usage, you'll always have to take care of this issue - no matter how many threads are - or will be - running.
Lucero
+1  A: 

While I agree with the comments you've already received on your question, the use of System.Environment.WorkingSet might perhaps be an actual answer to it if you really decide to take this course of action?

peSHIr