How to know available memory?

[s196675m]

I like to know how much memory is available in the system before I allocate any memory block. Is there any class or way to get the current memory information from the system. Thanks you for your help.

[PIEBALDconsult]

It could change between the time you check and the time you try to allocate anyway. Just try the allocation and catch the exception if any.

[Ennis Ray Lynch Jr]

Allocate the minimum amount of memory necessary for the given task. Also, in c# a memory allocation should not fail unless it exceeds the allowable limit set by the framework for the application, the slowness will be OS based thrashing from VM.

Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway

[s196675m]

Thanks for your suggession. Is there any way to know the amount of memory available programmatically even it might change from time to time. Just like taskbar, I like to know the snapshop of memory in any instance. Thank you again

[PIEBALDconsult]

s196675m wrote:

Just like taskbar

Not a wheel I would reinvent.

[s196675m]

Is there a way PROGRAMATICALLY( by code) to get memory information just like taskbar shows us.

[PIEBALDconsult]

I heard you the first time. I don't know of anything in .net (though maybe someone else does), but maybe pInvoke this: http://msdn.microsoft.com/en-us/library/aa366589(VS.85).aspx[^] P.S. I just tried it, it works, I might write an article on it sometime.

modified on Friday, May 16, 2008 11:10 PM

[s196675m]

Thank you for pointing me to the right API. I looked at the API's but I overlooked this function.

[PIEBALDconsult]

Glad to be of service.

[The Nightcoder]

Do you know how much memory you need to allocate or are you allocating "as much as you can" for some reason? If the former (you know what you need) - look at the System.Runtime.MemoryFailPoint in the later .NET versions. It was created to solve that need. If the latter (you don't) - consider rethinking your app. Seriously, stuff that does like that is a nuisance. Microsoft SQL Server and Exchange Server are two examples (using default settings). That's why they don't play well together in the same machine (without reconfiguring - and as Exchange requires direct Active Directory object property editing for that, it's even more of a nuisance). They keep fooling each others cache allocation strategies, and you end up with system requiring frequent restarts due to memory fragmentation.

-- Peter

[realJSOP]

Use System.Management and WMI API.

"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001