Max limits of Capabilities/PropertySets per SensorType/ThingType in IoT Services/Leonardo IoT

[fvviviani]

Dear Experts,

I wanted to try out some "flat" modeling on IoT Services/Leonardo IoT. I was wondering if there is any limit to the number of Capabilities that a SensorType can have, and on also to the number of PropertySets/Property that a ThingType can have.

I did not find any reference in the documentation so if there is, could you please point me to it?

Thanks and BR!

Federico

[former_member232287 · Accepted solution]

Hi Federico,

There is a recommendation to not use more than 200 properties in one property set type for performance reasons:

"For property set type of data category TimeSeriesData or DerivedData, you can define up to 500 properties. However, for better performance, we highly recommend you to define not more than 200 properties per property set type." [1]

Regards

Jan

[1] https://help.sap.com/viewer/fffd6ca18e374c2e80688dab5c31527f/2101a/en-US/6e7999e930054c46a5acc432901...

[fvviviani · Accepted solution]

Hello Jan,

Thanks a lot for your answer! On the opposite, is there a recommendation for the number of Property Sets that can be assigned to a Thing Type?

Thanks,

Federico

[former_member232287 · Accepted solution]

Hi,

I don't think there is a recommendation. Most API calls return the data by Property Set. So the number of different Property Sets shouldn't influence the performance of those noticeable. Of course there are a few APIs like the Snapshot API [1] where you query data across multiple Property Sets. Here it might be needed to use the select option and only get the properties you really need to don't have a performance impact.

But overall I would say it's better to split properties into multiple property sets instead of keeping them all in the same one.

Regards

Jan

[1] https://help.sap.com/viewer/fffd6ca18e374c2e80688dab5c31527f/2101a/en-US/650d94e61d7c487e9f16052938d...