Kepware tags limitations

[SL_10010290]

We are getting "Request pending" from Kepware IoT Gateway REST Server.
We have configured almost  - 10000+ tags for each site. We have CPU utilization remaining below 30%, indicating sufficient processing capacity for additional tasks. Network bandwidth is available, confirming that communication delays are not related to data congestion. 
We have only a single Kepware for all the sites. Does it going to impact our solutions?

[MKhatri]

Hi team,

I hope you're all doing well. I wanted to bring up a recent issue regarding the tags we've been working with. It seems that the 10,000 tags are not causing any problems, which is great news. However, I would like some clarification on the type of request that is being issued.

Are the rest server items configured for explicit read? If so, it's possible that device communication is causing a delay in the HTTP server response. On the other hand, if the rest server items are not configured for explicit read, the responses should be fast as they are returned from cache.

Could you please provide some more details on the type of HTTP request that is being issued - whether it's a GET or POST request (read or write)? It would also be helpful to see the source event log and project file to better understand the issue.

Thank you for your attention to this matter. Looking forward to resolving this issue promptly.

Regards,
Mohit