# Vision Client Request/sec

**URL:** <https://forum.inductiveautomation.com/t/vision-client-request-sec/70898>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [March 10, 2023, 11:23am UTC](https://forum.inductiveautomation.com/t/vision-client-request-sec/70898 "2023-03-10T11:23:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dominic\_Scalco](https://avatars.discourse-cdn.com/v4/letter/d/7ea924/32.png) [@Dominic\_Scalco](https://forum.inductiveautomation.com/u/Dominic_Scalco)\
**Post date:** [March 10, 2023, 11:23am UTC](https://forum.inductiveautomation.com/t/vision-client-request-sec/70898/1 "2023-03-10T11:23:52Z")

</div>

Good morning everyone,  
I have a question about the page Status --\>Vision Clients --\> Request/sec value. What requests are counted in this value? Is there a way to see how many requests are done by a single client instance?  
My problem is I have 2 distinct gataways with similar projects (not the same, but with similar logic and scope) on them , but one has about 100 requests/sec, the other one 3000 request/sec.

Thank you in advance,  
Dominic

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 11, 2023, 11:21am UTC](https://forum.inductiveautomation.com/t/vision-client-request-sec/70898/2 "2023-03-11T11:21:45Z")

</div>

The base client operation will produce requests based on the poll rate--4, 5, perhaps 10 per second. That covers your tag bindings and gateway=\>client push messaging. Pretty much everything else will be query bindings and scripting calls that need to request data from the gateway. I would consider even 100/second to be pathological.

Audit all of your bindings to find and eliminate unnecessary polling. Where many scripts are requesting things like alarm status, consolidate to a gateway script that populates a gateway memory tag, and bind that tag in the client where needed. Find and eliminate scripted `system.tag.read*()` calls that can be replaced with tag bindings or indirect tag bindings.