# Scanclass max speed

**URL:** <https://forum.inductiveautomation.com/t/scanclass-max-speed/18104>\
**Category:** General Discussion\
**Tags:** ignition79\
**Created:** [May 21, 2018, 8:32am UTC](https://forum.inductiveautomation.com/t/scanclass-max-speed/18104 "2018-05-21T08:32:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [May 22, 2018, 9:37am UTC](https://forum.inductiveautomation.com/t/scanclass-max-speed/18104/4 "2018-05-22T09:37:07Z")

</div>

> [@c.bertulli](#):
>
> I'm just looking to know which is the max speed at a tag can be read/write

It depends on load. Look at the actual statistics for the specific device, particularly the average response time. That's the round trip request from Ignition/response from PLC. Then look at the load factor. Anything close to or above 100% means there's not enough bandwidth (somewhere, usually the PLC) to satisfy all of the subscriptions at the requested pace (scan classes), slowing everything down. The more tags monitored, the slower it all gets.  
You can use the system.opc.\* functions to inject additional requests on demand -- those will perturb the statistics when used, but will execute as soon as possible. Round trip times from a gateway script using these functions will be notably faster than from a client script, of course.

---

_[View the full topic](https://forum.inductiveautomation.com/t/scanclass-max-speed/18104)._