Actually Chris, this is the way I have to perform some visualization
on my laptop is to set memory well above physical memory. However,
that does mean that its going to use VM (ie swap). And you want to
talk about slow. This will bring dx to a crawl when it is using disk
for RAM. So you are right in suggesting that he not force the memory
beyond physical RAM unless absolutely necessary.
David
?
768Mb Real + 768 Swap, I usually do a: dx -memory 1024 -edit blah.net
Huh, I never heard of anyone starting dx with memory greater than RAM. I
always let DX take care of this. The recommendation has always been 2-3x
RAM for swap, so maybe boost swap then start DX without the memory flag: it
should by default take 7/8 of available RAM. Maybe you are forcing it to
use swap in a way that is non-optimal. One of the IBM DXers have a comment
on the behavior in this case?
It is nevertheless a very large mesh for 768Mb. All those positions are
float 3-vectors. If you added color, you added another float 3-vector to
RAM for each position; then there's the data, etc. etc. Look into delayed
colors (byte lookup table) or do no coloring at this time (or use a
constant color). Remove (module) any unneeded components, Export the
stripped object and reimport it after Disconnect/restart server (only way
to truly garbage collect memory: Reset Server only flushes cache pointers
but leaves memory fractured, I believe).
Chris Pelkie
Vice President/Scientific Visualization Producer
Conceptual Reality Presentations, Inc.
30 West Meadow Drive
Ithaca, NY 14850
[EMAIL PROTECTED]
--
.............................................................................
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
