I'm not going to even to attempt to explain this one. Guy Robinson's blog Bolt Out of the Red has a new post yesterday that does. He's a programmer whose been specializing in Revit API projects for about as long as a person could be and not be a Autodesk employee.
I've responded to posts many times at AUGI asking this question or insinuating that Revit is slack for not doing this already. I think it is a much more important request to ask that performance overall be improved rather than state that the solution we want is "multi-threading" as if that alone solves the problem. I don't have the brains to even pretend to tell them how to solve it, I just want more, fasterer and betterer...soonererer. Thanks in advance for more, fasterer and bettererer.
Thanks Guy for your attempt to explain it!
Showing posts with label Multiprocessor. Show all posts
Showing posts with label Multiprocessor. Show all posts
Tuesday, February 02, 2010
Tuesday, August 18, 2009
Multi Core/Processors - Tech Note
In the Revit Tech Note document Autodesk has the following information:
Although the Revit platform is not fully optimized for multi-threading, multiple-core processors reduce cycle use by other applications running concurrently. Some reports show as much as a 20% increase in Revit platform performance in a multi-core or multiple processor environment.
In Revit 2010, multi-threaded methods for printing and wall join cleanup have been made available. Multi-threaded hidden line removal for printing has been enabled by default.
Due to the operating system overhead of maintaining multiple threads, multiprocessing of wall join cleanups can experience a minor degradation when only 2 CPU cores are present, but up to a 27% performance increase when 4 hyper-threaded CPU cores are present. Because 2 CPU core systems remain the most common configuration of Revit systems as reported by CIP data, multiprocessing of this features is OFF by default.
To enable multiprocessing for wall join cleanup, add the following entries to the Revit.ini file:
[PerformanceOptimizations]
ParallelWallJoins=ON
To disable multiprocessing for wall join cleanup, you may omit any entries in the
[PerformanceOptimizations] section of the Revit.ini file, or explicitly set the state of either one or both multiprocessing optimizations:
[PerformanceOptimizations]
ParallelWallJoins=OFF
ParallelPrintProcessing=OFF
The Revit platform's rendering function is optimized to use up to four processors. The Revit platform will share processing time with one of these four rendering processors, so there is no exclusive gain for the Revit platform in making more than four processors available. Additional processors may be desired if other computationally intensive applications need to run while the Revit platform is rendering.
Also, if you use the 3.5 GB switch feature for Windows 32 bit operating systems Revit is already a Large Address aware application so no additional work is required other than enabling the switch.
Although the Revit platform is not fully optimized for multi-threading, multiple-core processors reduce cycle use by other applications running concurrently. Some reports show as much as a 20% increase in Revit platform performance in a multi-core or multiple processor environment.
In Revit 2010, multi-threaded methods for printing and wall join cleanup have been made available. Multi-threaded hidden line removal for printing has been enabled by default.
Due to the operating system overhead of maintaining multiple threads, multiprocessing of wall join cleanups can experience a minor degradation when only 2 CPU cores are present, but up to a 27% performance increase when 4 hyper-threaded CPU cores are present. Because 2 CPU core systems remain the most common configuration of Revit systems as reported by CIP data, multiprocessing of this features is OFF by default.
To enable multiprocessing for wall join cleanup, add the following entries to the Revit.ini file:
[PerformanceOptimizations]
ParallelWallJoins=ON
To disable multiprocessing for wall join cleanup, you may omit any entries in the
[PerformanceOptimizations] section of the Revit.ini file, or explicitly set the state of either one or both multiprocessing optimizations:
[PerformanceOptimizations]
ParallelWallJoins=OFF
ParallelPrintProcessing=OFF
The Revit platform's rendering function is optimized to use up to four processors. The Revit platform will share processing time with one of these four rendering processors, so there is no exclusive gain for the Revit platform in making more than four processors available. Additional processors may be desired if other computationally intensive applications need to run while the Revit platform is rendering.
Also, if you use the 3.5 GB switch feature for Windows 32 bit operating systems Revit is already a Large Address aware application so no additional work is required other than enabling the switch.
Subscribe to:
Posts (Atom)