# Tag history binding slows system

**URL:** <https://forum.inductiveautomation.com/t/tag-history-binding-slows-system/113511>\
**Category:** Ignition\
**Created:** [January 23, 2026, 12:19pm UTC](https://forum.inductiveautomation.com/t/tag-history-binding-slows-system/113511 "2026-01-23T12:19:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![thimo\_van\_den\_broek](https://avatars.discourse-cdn.com/v4/letter/t/7ba0ec/32.png) [@thimo\_van\_den\_broek](https://forum.inductiveautomation.com/u/thimo_van_den_broek)\
**Post date:** [January 23, 2026, 12:19pm UTC](https://forum.inductiveautomation.com/t/tag-history-binding-slows-system/113511/1 "2026-01-23T12:19:26Z")

</div>

Hi,

I’m working on some trending views and currently facing some performance issues.

I have one view where I show 8 trends with each 2 pens

When I open the view with the trends, the gateway cpu starts spiking to 70% where it is at 6% when viewing a screen that does not have trends.

The query throughput of the core historian (historian.IgnitionCoreHistorian.query.throughput.actual) average at 400 queries per second (0 when not viewing trends)

This seems excessive to me for 16 pens x 100 points

Anyone a idea what I’m doing wrong?

Using the config:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/c/3cddd7d2fb704cbffcfe683de5f7a560652a1ffc.png)

custom.output is : [

{

```
"aggregate": "SimpleAverage",

"alias": "PV DCI Speed",

"path": "\[default\]204/501/011/Act_Speed"

```

},

{

```
"aggregate": "SimpleAverage",

"alias": "SP DCI Speed",

"path": "\[default\]204/501/011/Act_Speed" }

```

]

I don’t think it’s a logging problem but here is the logging config

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/2/d27e61a187e11c1a03117e8c22c8373dfeddee03.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:** [January 23, 2026, 1:37pm UTC](https://forum.inductiveautomation.com/t/tag-history-binding-slows-system/113511/2 "2026-01-23T13:37:44Z")

</div>

Don't use realtime mode for many pens, unless you set the chart to update very slowly.

(Ignition queries the entire realtime span for every update. It's caching system can't really handle this.)

---

<div class="post-metadata">

**Author:** ![thimo\_van\_den\_broek](https://avatars.discourse-cdn.com/v4/letter/t/7ba0ec/32.png) [@thimo\_van\_den\_broek](https://forum.inductiveautomation.com/u/thimo_van_den_broek)\
**Post date:** [February 2, 2026, 1:54pm UTC](https://forum.inductiveautomation.com/t/tag-history-binding-slows-system/113511/3 "2026-02-02T13:54:41Z")

</div>

does the system.historian.queryRawPoints also queries the entire realtimespan? the disadvantage of the historical tag history is that it does not update every so often

---

<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:** [February 2, 2026, 2:00pm UTC](https://forum.inductiveautomation.com/t/tag-history-binding-slows-system/113511/4 "2026-02-02T14:00:19Z")

</div>

Not sure. That function is new for v8.3 and I haven't dug too deeply into it yet.

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [February 2, 2026, 2:17pm UTC](https://forum.inductiveautomation.com/t/tag-history-binding-slows-system/113511/5 "2026-02-02T14:17:27Z")

</div>

> **[Real Time Trend Seed from historian, and Feed from tag value | Ignition...](https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/real-time-trend-seed-from-historian-and-feed-from-tag-value)**
>
> It would be nice to have a real time trend option where the chart will grab the designated range of data from the historian, but then update the live dataset

This would be lovely, and bring it on par with other scada trending charts.