Matrix Capacity

[CharlieEVIEWS]

Dear all,

Could somebody possibly provide some details on the maximum permissible number of matrix elements? Cant see any information on http://www.eviews.com/EViews9/ev9capacity.html? It seems a 625m element matrix is too large. I guess I could write a short program to sequentially test the boundary with increasing increments, but might be not be the fastest thing to do :)

Is it a a hard threshold as opposed to one that's curtailed by hardware/subject to system requirements?

Best wishes as always!

Charlie

[EViews Gareth]

I believe rows*(cols+1)<268,435,424

[CharlieEVIEWS]

Interesting crash bug: when i just tried to create a second (large) matrix to test near to the limit, i got a 'stopped working' message. Undoubtedly due to the fact I'm on a 4gb laptop only, but a warning message might be cooler than a crash bug

As a test, I then ran:

Code: Select all

wfcreate u 1 for !a = 1 to 999999 matrix(10000,10000) matrix_!a next

And I got to 3

[EViews Gareth]

It is very difficult to error politely when you run out of memory :(

[startz]

Interestingly, I did not get a crash. After 80 matrices things slowed down a lot. That's about right on my 64GB machine. Wonder if the bug has to do with 32-bit versus 64-bit.

[CharlieEVIEWS]

I'm running 64bit EE on this system, which is just curtailed by RAM size. I bet if you changed 10000 to ~16000 and let it run for a few hours, you'd see the same crash even with 64gb of ram...

[startz]

So it sounds like a bug from a failed memory allocation. My machine would just take longer to hit.

Perhaps for debugging purposes they should dig out the Apple II that the program ran on originally. I think it had 48k of memory.