Re: How to use a huge memory in C#?

Tech-Archive recommends: Fix windows errors by optimizing your registry


"Chris Mullins" <cmullins@xxxxxxxxx> wrote in message
news:OBweV7L7GHA.4568@xxxxxxxxxxxxxxxxxxxxxxx
| Sure enough. A quick Google Search agrees with you.
|
| I wonder if the last time I tried was v1.0? I don't think it's been that
| long.
|
Could be, but it could be something else....

| I do remember at that time (we were doing extensive profiling), we wanted
to
| host our Server using the Server CLR, not the Workstation CLR. I needed to
| write a C++ hosting exe to do this. If I remember right, that means it
must
| have been 1.0, since in 1.1 CLR selection was a config file entry.
|
Keep in mind that the /4GT RAM tuning introduces another serious issue, that
is OS resource exhaustion, most of the time it doesn't solve anything, this
trick was invented by MSFT specifically to give MSQL and Exchange some more
headroom.
Also, keep i mind is that this extra GB is separated from the lower 2GB by
the loaded modules (DLL's) and an additional 64KB gap. That means that you
don't get a contigious memory block of 3GB to allocate, so if you think you
can now create a 2GB byte array, you will soon find out that you can't.
Fragmentation bytes again ;-)

| Ah well. I'm probably just confused. We've been 64-bit for a while now, so
| this just doesn't come up for me anymore. Anytime a customer asks "how big
| can it scale?" we just give out the 64-bit numbers.

Absolutely right, whenever your application needs more than 2GB, move to 64
bit.

Willy.





.