Revit Database Optimisation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I am interested in some insight as to optimisation of a Revit project database.
This post highlights that geometry complexity (and size) can be affected by internal structures that are not visible or logical to the end user.
http://forums.autodesk.com/t5/revit-api/model-size-increase-with-reduced-elements/m-p/5970811#M13488
The one part version of the LeftCurveElementRing has the two curved surfaces represented by Hermite surfaces consisting of 1089 point nodes totaling 2178 point nodes. In the six part version, the curved surfaces are represented by 12 Hermite surfaces of 81 point nodes each and 12 Hermite surfaces of 4 point nodes each, totaling 1020 point nodes.
Specifically, I want to be able to run a QA process for a Revit file. It is easy to look for the obvious: Size and numbers of Groups, Elements, Families, etc. What is less obvious is a means to analyse the geometry and embedded data that may have an impact on the physical size and processing load for a Revit model. It goes beyond geometry; what impact do lengthy parameter formulae have? Complex nested Families? Hosting and constraints?
Obviously this is a lot to cover, but I thought to start with geometry and see where it ends up. Given the above example, has anyone developed a GeometryDump? Jeremy's post will be a start for me: http://thebuildingcoder.typepad.com/blog/2010/01/geometry-options.html
Dale
______________
Yes, I'm Satoshi.