>> What are you seeing while Pick'ing? i.e. if you are drawing all those
>> connections that must ugly; if you are drawing all those planes with some
>
>The Pick was a test to see how long one interpolation takes. At
>the moment I am rendering one Slab, and do the Pick in the Slab.
>As I said this takes 10-15s. Reducing the volume reduces the
>amount of time it takes for the Map. It would appear as if the
>regularity of the field is lost along the way and Map is happily
>processing each point.
Easy to find out. Truly regular means the connections are still defined as
a mesh array, so attach Print("rd") to the object and take a look. If you
see a long list of 8-vectors of int for connections, then, yes, you have
lost the regular definition even if the connections are inherently regular.
You can regain them by Constructing a mesh of the identical grid counts and
Replacing the connections from this mesh onto your mesh. Or go back and
look into where in the process your connections stop being a compact mesh
array and are expanded and see if you can avoid the operation that causes
them to expand (not always possible of course).
>?
>
>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]
