Is there a point when Ontology Objects have too many properties?

Ask the Community
1

We have many large objects, and want to confirm if there is a point where we should split out ontology objects into parts versus adding more properties into one

2 Likes
2

Hey Raj! the limit is 2,000 properties for OSV2

3

One more aspect to think about, in addition to the OSv2 limit, is usability and legibility of your ontology, and when does it become hard to manage an object that has too many properties to scroll through.

4

hey @krasi @arochat ! Thanks for your responses :slight_smile:

I’m also curious to know how the number of properties in an ObjectSet would affect things like rendering visualizations (/aggregations) in Workshop, such as with an embedded Quiver dashboard…

e.g. If i have a Quiver Vega plot embedded in a Workshop module → when I pass in an objectSet of 100k Objects to the widget, do all 2k properties get loaded into memory for each object (i.e. 200m in total)? Or do only the “relevant properties” for the aggregation/visualization get loaded? (This could be as few as 2-3 properties per object → or 2-300k in total)

“memory” here being either the browser, or any back-end service memory

Depending on which approach the platform takes, I guess the performance implications of Workshop modules could be significant