iModel

Purpose

The iModel tab displays common element queries for the current imodel.

iModel Performance : indicates hte query performance for the current user with the current iModel. The first query is generally slow, but caching performance on toolbox means that generally subsequent queries will alwways be classed as good.

Save : The Save option allows trends in the carious counters to be tracked Download : Enables downloading of results into a spreadsheet.

• Elements : The total number of elements in the iModel
• Models : The total number of engineering models in the iModel. Depending upon the source engineering content, this can range from a few models to many hundreds. More is not always better.
• Classes : The total number of defined classes in the iModel. This should be checked against the number of "Used" classes in the iModel a big delta between classes and utlised classes is generally a bad sign
• Aspects : the number of aspects records. Note ExternalSourceAspect can skew these results, but generally 1000's of aspects records and aspect classes can make your iModel difficult to utilise as a trusted data source.
• Relationships : The number of relationships in the iModel. Tends to be the slowest query to return results.
• Geometry : The number of geometric elements in the iModel. Should not be a magnitude lower than the number of elements.

Note

This is a selection of standard queries we use to benchmark iModels / Users / Locations for performance purposes All queries on this becnhmark are not cached. Refer to the benchmark page for additional information