If many devices are pushing multiple properties very frequently and the error message code 1114 appears in the logs, you may need to change the default timeout for the ThingWorx Platform to respond to a service call. For details, refer to Troubleshooting an Error Pushing/Persisting Properties and Property Lists.

BEST PRACTICES: For best performance, do not push every time a property changes. Collect property updates and send them in batches to the ThingWorx Platform. It takes anywhere from 3 to 500 ms for a round-trip to the ThingWorx Platform from the device. You want to get the most value for each round trip. Sending in batches makes that possible. It may take experimenting with different batches. For example, you could start at 100 updates, then increase to 500, and then 1000. When you have achieved a batch number that gives you the desired performance, then test that over time. You need to take into consideration the traffic on your network as well as the load on the database when updating too frequently. For example, pushing every 3 ms can put a lot of load on a relatively small database. Monitor how many property updates come in on a regular basis. Your environment and organizational needs can help determine if and when you need to re-evaluate how many updates you send in each batch and how often. Also, keep in mind that there is a small latency between the arrival of an update at the platform and its display in a mashup or in ThingWorx Composer.