Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
Hi
I am developing a data model that will contain a single view with many properties (approx. 150). The number of properties will probably also increase over time. To model this, I have tried splitting the data in two containers and mapping the properties in the view to both containers. However, now that I am testing it I am experiencing performance issues. I have now tested the model with 3 million instances and all queries time out.
I am therefore wondering if there are any recommended/tested approaches for dealing with wide tables in data modeling that will make it more efficient.
The data model mostly contains normal properties (string, float, int) and 4 direct relation properties. I have created three indexes on one of the containers on properties that I need to filter on in queries.In addition, the view implements the CogniteDescribable and CogniteSourceable concepts from the core model.
Thank you!
