# Device status request count & Throughput

**URL:** <https://forum.inductiveautomation.com/t/device-status-request-count-throughput/34475>\
**Category:** Ignition\
**Created:** [May 6, 2020, 5:21am UTC](https://forum.inductiveautomation.com/t/device-status-request-count-throughput/34475 "2020-05-06T05:21:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yfactor](https://avatars.discourse-cdn.com/v4/letter/y/e79b87/32.png) [@Yfactor](https://forum.inductiveautomation.com/u/Yfactor)\
**Post date:** [May 6, 2020, 5:21am UTC](https://forum.inductiveautomation.com/t/device-status-request-count-throughput/34475/1 "2020-05-06T05:21:38Z")

</div>

Hi there, If the request count per sec is more than the throughput (1 min), does that mean that the tag update will be slower?

 ![Capture](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/338c49800eb59245c6b611d9acf6c0b8e9ff8c98.png)

---

<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 6, 2020, 12:16pm UTC](https://forum.inductiveautomation.com/t/device-status-request-count-throughput/34475/2 "2020-05-06T12:16:36Z")

</div>

Yes, normally. But your displayed load factor suggests there’s some other optimization impacting your case.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [May 6, 2020, 12:28pm UTC](https://forum.inductiveautomation.com/t/device-status-request-count-throughput/34475/3 "2020-05-06T12:28:07Z")

</div>

The throughput suggests your tags subscribed @ 2000ms are updating just a little slower than that.

Load Factor is a strange calculation that I’d like to replace eventually. It’s calculated like this, using the 50th percentile from the histogram:

```auto
var loadFactor = Math.round(histogram['p50'] * requestCount / concurrentRequests / rate * 100);

```

Basically… it’s a crude measurement of the remaining “capacity” of the connection based on the 50th percentile request/response latency. I’m not convinced it’s very useful or accurate any more, and it seems to fall apart when concurrentRequests \> 1 and/or there are multiple rate groups.

---

<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 6, 2020, 12:34pm UTC](https://forum.inductiveautomation.com/t/device-status-request-count-throughput/34475/4 "2020-05-06T12:34:09Z")

</div>

It also doesn’t account for writes or out-of-band traffic (system.opc.\*).

---

<div class="post-metadata">

**Author:** ![Yfactor](https://avatars.discourse-cdn.com/v4/letter/y/e79b87/32.png) [@Yfactor](https://forum.inductiveautomation.com/u/Yfactor)\
**Post date:** [May 8, 2020, 6:18am UTC](https://forum.inductiveautomation.com/t/device-status-request-count-throughput/34475/5 "2020-05-08T06:18:25Z")

</div>

One more question @pturmel or @Kevin.Herron,  
I tried to look at the manual for the meaning of “Tag Count” but couldn’t find it…  
Tag Count means the total no. of tags for the Request Count?

Cheers

---

<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 8, 2020, 12:12pm UTC](https://forum.inductiveautomation.com/t/device-status-request-count-throughput/34475/6 "2020-05-08T12:12:23Z")

</div>

Basically, yes. Subscribed items, typically Ignition’s OPC tags. Can also be elements in a SQL Bridge transaction group.