Re: 64-bit memory consumption

One has to wonder what the point of using .Net to target 64bit would be, since two important benefits are negated by design:
- GC already has trouble coping with hundreds of megabytes worth of
objects, and with gigabytes, it's not really improving (euphemism).
- IL doesn't support vector floating-point, so the benefits of
standardized SSE2 support are lost.
- JITter (so far) doesn't seem to be able of making good use of the
extra registers, this may improve, but there are still quite a few
roundtrips to memory and stack juggling in there, unless you're lucky
enough to hit one of the few peephole optimizations.

A side effect of larger pointers in .Net is that as objects get bigger, they also become more likely to end up in generation 1+, which are less often GC'ed, and thus it ends up inflating memory usage even more.

Eric
.