Yes. You may have heard reference to the "Network from Hell". That was ours (at least when I was at the EPA). It was around 2000 modules plus 1200 in macros (not including instances). The net was so slow that on a simple 30x30 grid (single layer) the frame rate was 3 secs per frame.
Greg originally believed that it was the Switch and Route nodes that were killing us. We had over 500 of these in the top level of the net. The executive has to check these on every iteration, so the more you have the slower you go. The trick is to bury as many as possible into macros so they aren't checked every execution. The second idea was to dump the ui completely, and replace it with custom code. I had some good results initially, but that was working on a subset of the net. Randall wrote a python app that reads the net, extracts the ui elements, and replaces them with python ui elements (I presume they were Tk). It was pretty slick. However, once applied to the full network, our performance went in to the toliet again. We never had much luck in getting the performance up from the super-slow rate, other than trimming the network into pieces. Mark -- ---------------------------------------------------------------------- Mark A. Bolstad [EMAIL PROTECTED] Raytheon Systems Company (410)278-9149 Scientific Visualization Specialist U.S. Army Research Laboratory - HPC Major Shared Resource Center ----------------------------------------------------------------------
