To all concerned, don't forget about the Optimize Cache menu option.
This does a pretty good job for normal running, but you can still
override its decisions in extreme cases.
On Friday, January 17, 2003, at 05:02 AM, Mattijs Janssens wrote:
Lloyd A Treinish wrote:
In addition to Chris' suggestions, make sure that you do have
requested as
much memory (or memory+swap) that you can because of all of the
geometry
being generated. If you don't have anything else that you need to
run,
then do dx -memory 2048 (assuming you have 2 GB of swap). Also, I
have
found that optimizing memory usage in the net and the net's
organization
can have a big impact.
About optimizing memory usage: an interesting feature of the network
editor is that the default cache status of most(all?) modules added is
'Cache All'. I found that after every edit session I had to be very
careful in making sure that all cache states were set to 'Cache Last'.
This is ofcourse only nessecary if like me you run too many programs
on too small a machine and DX runs (partially) from swap.
Regards,
Mattijs
Chris Pelkie
Vice President
Conceptual Reality Presentations, Inc.
30 West Meadow Drive
Ithaca, NY 14850
