Memory allocation and zeroing out...

[Atmapuri]

Hi!

It seems that every memory allocated by the garbagge collector
is zeroed out (an array is set to all zeros).

Is there any way to allocate memory via garabage
collector without having that automatic zero out feature?

In my case that zero out is adding a serious performance penalty.

Thanks!
Atmapuri

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

Hi!

It seems that every memory allocated by the garbagge collector
is zeroed out (an array is set to all zeros).

Is there any way to allocate memory via garabage
collector without having that automatic zero out feature?

This has no sense, what will happen then when you create a new instance? You
will have garbage.

In my case that zero out is adding a serious performance penalty.

I can assure you that your problem resides somewhere else.
Post back with more details and code and let's see what is going on.

 

[Ben Voigt [C++ MVP]]

Hi!

It seems that every memory allocated by the garbagge collector
is zeroed out (an array is set to all zeros).

Is there any way to allocate memory via garabage
collector without having that automatic zero out feature?

In my case that zero out is adding a serious performance penalty.

Then reuse the object, instead of letting it be collected. If you are
allocating memory too fast you will have performance problems due to running
the GC too often, and the zeroing cost is a very small part of the price you
pay.