Hi Peter,
Thank you for your suggestion. I increased the virtual memory to 2.5 GB,
decreased the number of points to from 1.7 million to 836,000 and after
letting it chug for over 1 hr. I gave up and ended the task. I increased
the virtual memory to 4 GB and saw no difference. This seems to indicate
that the virtual memory is not the culprit in this case. When I displayed
418,000 points with 2 GB virtual memory, the image came up in a couple of
minutes. In both cases, I am using ShowPosition rather than Glyphs.
Is there some setting for page swapping in DX? Would a dedicated graphics
board work better and if so, which board?
Thanks.
Gerry
At 01:51 PM 8/31/2001 +0200, you wrote:
Hi Gerry
No, I doubt it is the machine, we also run big data sets on similar spec.
machines (upto 1GB RAM) and find that image can be slow but gets there
eventually. The important thing is to may sure there is enough memory
space (virtual if not physical) assigned, so that the module can realloc
successfully. Use the "-memory " switch to specify 2GB (assuming your NT
swap file is bigger than that) and then sit back and wait.....
If you are using glyphs, make sure you use the "speedy" optio. This really
cuts down on the processing time. If we need fancy symbols for publication
plots etc, we use "normal" or "spiffy" when you need to make the plots,
but for "work" we use the simple stuff.
Peter
At 18:06 30/08/2001 -0400, you wrote:
Hi,
I am trying to display about 1.7 million data points in DX. My PC is
WinNT and has 640 MB RAM, 32MB video card, and has Exceed installed. The
program hangs-up when it gets to the image module. Is there a memory
problem with my PC, Exceed, video card?
Thanks.
Gerry
