comp.lang.idl-pvwave archive: archive » Re: Large array memory problem.

Home » Public Forums » archive » Re: Large array memory problem.

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Large array memory problem. [message #46400 is a reply to message #46398]

Tue, 22 November 2005 11:14

Mark Hadfield
Messages: 783
Registered: May 1995

Senior Member

Carolina wrote:
> Yes, I was using Windows. I remember seeing some articles in this
> websites that mentioned how to get a couple of mb more of memory, but
> that is definetly not good enough for what I want to do. I didn't think
> it was related to memory fragmentation, since this problem is present
> even with a new IDL session, without any other arrays defined
> previously. I am currently working in a unix machine and I can now
> access around 4gb of memory, and I can allocate 3 complex square arrays
> with dimensions 11000 by 11000, as long as they aren't double precision
> (these occupied 2.9gb all together). It wouldn't let me allocate 2
> double precision ones (these would take about 4gb).

There is an IDL procedure called memtest (or mem_test) that will report
on the areas of *contiguous* memory available to IDL. You can get it here:

http://www.rsinc.com/services/techtip.asp?ttid=3441

You might might want to look here as well:

http://www.rsinc.com/services/techtip.asp?ttid=3512

On my system (Windows 2000 Service Pack 4, 1 GiB RAM, a few GiB of swap
space), when IDL is freshly started, memtest reports the following

Memory block # 1: 1033 Mb (total: 1033 Mb)
Memory block # 2: 388 Mb (total: 1421 Mb)
Memory block # 3: 203 Mb (total: 1624 Mb)
Memory block # 4: 61 Mb (total: 1685 Mb)
Memory block # 5: 58 Mb (total: 1743 Mb)
Memory block # 6: 48 Mb (total: 1791 Mb)
Memory block # 7: 33 Mb (total: 1824 Mb)
Memory block # 8: 21 Mb (total: 1845 Mb)
Memory block # 9: 20 Mb (total: 1865 Mb)
Memory block #10: 17 Mb (total: 1882 Mb)

(where the "Mb"s are supposed to be "MB"s, ie megabytes rather than
megabits).

I doubt that you're goin gto do much better than this in Windows.

--
Mark Hadfield "Kei puwaha te tai nei, Hoea tahi tatou"
m.hadfield@niwa.co.nz
National Institute for Water and Atmospheric Research (NIWA)

Report message to a moderator

[Message index]

		Re: Large array memory problem. By: Rick Towler on Tue, 22 November 2005 11:23
		Re: Large array memory problem. By: Mark Hadfield on Tue, 22 November 2005 11:14
		Re: Large array memory problem. By: Pitufa on Tue, 22 November 2005 10:49
		Re: Large array memory problem. By: Paolo Grigis on Tue, 22 November 2005 05:34
		Re: Large array memory problem. By: news.qwest.net on Wed, 23 November 2005 08:26
		Re: Large array memory problem. By: Rick Towler on Mon, 28 November 2005 16:34
		Re: Large array memory problem. By: Greg Hennessy on Tue, 22 November 2005 15:45
		Re: Large array memory problem. By: R.Bauer on Sun, 27 November 2005 01:22
		Re: Large array memory problem. By: Nigel Wade on Thu, 24 November 2005 01:40

Previous Topic:	Re: My code is way to slow.. How can I optimize!?
Next Topic:	the fastest way to find number of points in sphere(radius r)

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 12:30:45 PDT 2025

Total time taken to generate the page: 1.68311 seconds