Skip to main content
16-Pearl
February 6, 2026
Solved

Calling a ThingWorx service every 10 seconds – is this acceptable?

  • February 6, 2026
  • 3 replies
  • 124 views

 

Hi everyone,

I have a use case where a client application calls a ThingWorx service every 10 seconds.
The service is very lightweight and only returns a single property value (no database queries, no file access, no loops).

From a ThingWorx performance and best-practice perspective:

 

  • Is this polling interval considered acceptable?

  • Are there any concerns regarding scalability or platform load for such a setup?

Any guidance or experience-based feedback would be appreciated.

Thanks in advance!

Best answer by slangley

Hi @MA8731174 

 

Polling a ThingWorx service every 10 seconds can be acceptable for lightweight services that return a single property value, especially if there are no database queries, file access, or loops involved. However, there are several considerations regarding performance, scalability, and platform load:
 

Performance Impact: While the service is lightweight, frequent polling can still add up, especially if multiple clients are making similar requests. It's essential to monitor the overall load on the ThingWorx platform to ensure it can handle the cumulative requests without degradation in performance.
 

Scalability Concerns: If the number of clients increases or if the polling frequency is reduced, the load on the platform could become significant. It's advisable to assess the expected growth in client connections and adjust the polling strategy accordingly.
 

Best Practices: To optimize performance and reduce potential issues, consider implementing strategies such as:

  • Using event-driven architecture or webhooks instead of polling, if applicable.
  • Caching results where possible to minimize repeated calls for the same data.
  • Monitoring service execution times and memory usage to identify any bottlenecks.

For further insights and best practices, you can refer to the following resources:
 

 

Regards.

 

--Sharon

3 replies

slangleyCommunity ManagerAnswer
Community Manager
February 9, 2026

Hi @MA8731174 

 

Polling a ThingWorx service every 10 seconds can be acceptable for lightweight services that return a single property value, especially if there are no database queries, file access, or loops involved. However, there are several considerations regarding performance, scalability, and platform load:
 

Performance Impact: While the service is lightweight, frequent polling can still add up, especially if multiple clients are making similar requests. It's essential to monitor the overall load on the ThingWorx platform to ensure it can handle the cumulative requests without degradation in performance.
 

Scalability Concerns: If the number of clients increases or if the polling frequency is reduced, the load on the platform could become significant. It's advisable to assess the expected growth in client connections and adjust the polling strategy accordingly.
 

Best Practices: To optimize performance and reduce potential issues, consider implementing strategies such as:

  • Using event-driven architecture or webhooks instead of polling, if applicable.
  • Caching results where possible to minimize repeated calls for the same data.
  • Monitoring service execution times and memory usage to identify any bottlenecks.

For further insights and best practices, you can refer to the following resources:
 

 

Regards.

 

--Sharon

19-Tanzanite
February 9, 2026

HI @MA8731174 

As stated in other similar posts in the past, this depends entirely on your load. There are two things I strongly recommend to do:

1. Build a JMeter stress test with a tens of threads to simulate your users. See how the platform behaves. 

2. Make sure to use already existing JSESSIONID for the next requests. Typically in the whole TLS request process it's the initial TLS Handshake which takes a lot of CPU time, which at scale will impact you. 

Community Manager
February 17, 2026

Hi @MA8731174 

 

If you feel your question has been answered, please mark the appropriate response as the Accepted Solution.

 

Regards.

 

--Sharon