cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

DotNet SDK - Best way to implement queue and buffering to update properties

Gravel

DotNet SDK - Best way to implement queue and buffering to update properties

We have various properties that are updating very frequently. What will be the best way to implement this using the .Net SDK?

Do we need to create separate threads to update properties?

Current code looks like this, which is the default implementation, however for properties that are updating very frequently, what would be the best way?

 

targetThing.setProperty(propertyName, value);

targetThing.updateSubscribedProperties(15000);

 

4 REPLIES 4

Re: DotNet SDK - Best way to implement queue and buffering to update properties

How to achieve maximum throughput, using both these?

Do I need to create separate threads for both SetProperty and UpdateSubscribedProperties ?

 

Tags (1)

Re: DotNet SDK - Best way to implement queue and buffering to update properties

Hi @Shivaji.

 

When you say the properties are updating very frequently, how often is that?  What version of the DotNet SDK are you using?

 

Regards.

 

--Sharon

Re: DotNet SDK - Best way to implement queue and buffering to update properties

We have several devices that have more than 300 properties which are updating every second. 

Re: DotNet SDK - Best way to implement queue and buffering to update properties

My bad, the devices have more than 500 properties which are updating every second. 

Using following version of .net SDK.

MED-61061-CD-055_M050_Dotnet-SDK-5-7-6-3407-win-fips

Also I believe the setProperty adds properties in a queue and the updateSubscribedProperties pushes them to platform. 

What is the limit of this queue? Is it possible we can set the limit of this queue?

Will it work fine in our case of more than 500 properties per device for several devices?

I heard PTC is going to implement property sets for updating list of properties, but that is on platform side. Will there by any change in the sdk for this?

Announcements

Thingworx Navigate content has a new home! Click here to access the new Thingworx Navigate forum! ______________________________