comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: problems plotting LARGE amounts of 2D data?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: problems plotting LARGE amounts of 2D data? [message #1725 is a reply to message #1723] Tue, 22 February 1994 09:22 Go to previous message
thompson is currently offline  thompson
Messages: 584
Registered: August 1991
Senior Member
mcheng@dunlop.cs.wisc.edu (Michael Cheng) writes:


> Hi

> I am trying to find ways to plot LARGE amounts of 2D data,
> and I like to know what is currently the state of the art. For the
> sake of this posting, let's say "large" means much more data than
> fits in real memory. From my own experience, using the virtual memory
> of the workstation to store large amounts of data impedes performance
> due to excessive paging. Here is what I have been able to gather so far:

> 1) AVS: has 25,000 point limit. Everything is loaded into virtual memory.

> 2) Khoros 1: loads everything into virtual memory.
> Any updates from Khoros 2.0?

> 3)idl/pvwave: As far as I can tell from the short demo,
> loads everything into virtual memory?

> I'm posting this to the various Comp.graphics.*
> groups, hoping that I can get feedback from users of various software
> packages. I would appreciate comments on the current/future capabilities of
> the above packages. I would also like comments about other
> packages, such as SGI Explorer, IBM Data Explore, apE, or any other
> package. Thanks in advance.

> Mike

I think the way you're looking at this is all wrong. It's not AVS/Khoros/IDL
which decide whether or not data are in real or virtual memory--it's the
operating system. Operating systems such as Unix or VMS shield the program
from knowing how much of the memory they're using is real or virtual.
Generally speaking, you'll get as much of the real memory as possible and only
the overflow will be stored in virtual memory. Any programs which are designed
to run on a virtual memory operating system should behave the same way.

If a program such as IDL (or any of the others you mention) is putting things
into virtual memory, it can only be because you don't have enough real memory
available to you. The only thing you can do is buy more memory, or if your
operating system supports memory usage quotas (such as VMS) then you need to
increase your quotas.

Bill Thompson
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Emacs mode for .pro files???
Next Topic: Problems with Server Mode

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 08:31:35 PDT 2025

Total time taken to generate the page: 0.56344 seconds