I heard that there is a hard limit on the size of .Net Array. It is said that the maximum amount of memory that can be allocated to any single instance of an Array object ( regardless of whether it's int[], double[] or your own array) is 2GB. And no, if you have a 64 bit machine, the 2GB limit is still there.
I'm not sure whether my impression is correct or not. Anyone can confirm?
That is correct. No single object can be larger than 2 GB.
As with 32-bit Windows operating systems, there is a 2GB limit on the size of an object you can create while running a 64-bit managed application on a 64-bit Windows operating system.
This question has additional details and some useful links: http://stackoverflow.com/questions/1087982/single-objects-still-limited-to-2-gb-in-size-in-clr-4-0
I would have thought that the limit might be on the index. I thought that index used has to be an integer so anything bigger than integer wouldn't work unless they have some way around that. So that would be 4294967296 elements. Not sure if this is even half true. I would like to know the answer myself.
EDIT: As tomtom pointed out, integer is usually signed unless they using a non signed integer. So half of 4294967296 or 2147483648 roughly.
You will run into a practical limit first - it is pretty impossible to ge a 2gb array allocated. Practical limtis I have encountered are around the 800mb mark AT PROGRAM START - going down drastically after that.
Anything larger than 64mb is a luck gamble on 32 bit - the large object heap is not defragmented, so you need 65mn free in one piece or allocation fails.
Theoretical limits are:
But seriously, the practical implications are larger.
For .NET 4.0.... consider using memory mapped files ;)
Hope this help: http://blogs.msdn.com/joshwil/archive/2005/08/10/450202.aspx
i.e. 1. It uses int as index, which has max value = 2,147,483,647 (2GB) 2. Its by design.