You wouldn't want to cache them all, just the ones with important
calculations. For example if you have a line of modules say
Import->Mark->Compute->Unmark->AutoColor, then your best bet is to
say cache off on all but the AutoColor module because you don't need
any of the intermediate results.
David
All modules, the cache has been set to Last results.
At 05:17 PM 5/1/2002 -0600, you wrote:
for each module, what is the cache? (select the module, edit menu,
configuration)
-randy polson
On Wed, 1 May 2002, Geraldine Cheok wrote:
Hello all,
I have a DX script to display 4 points clouds with about 400,000 points
each and it ran slowly on my laptop (Windows 2000, CPU 1.3 Ghz, 512 MB RAM,
NVIDIA GE Force 2 graphics card). As I mentioned in a earlier message to
the group, the script re-imported the data every time I
rotated/scaled/moved the image.
I tried running the same script on a desktop with dual processors (2 GHz
each), Windows 2000, 2 GB RAM, Wildcat II graphics card with 128 MB
memory). I didn't see a difference in performance - the files were
re-imported for every move. I tried dx - optimize memory - I didn't see
and difference in terms of speed of re-displaying the image and got some
pretty strange images. When I tried dx -memory 1900, I got a message about
the localhost was queued. Is there some setting or flag that has to be set
that I am missing.
Thanks for any suggestions in advance.
Gerry Cheok
--
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
