I wonder why we see performance issues when we have a dataset size of more than 3000 rows in Perspective Table which causes the page to freeze, gateway crash, and so on, but the SQL IDE tools can simply read and display more than 20000 rows easily. What is the mean difference between these two?

Simple. SQL IDE like Datagrip or the native tools for a particular DB platform don't convert everything to JSON.

But QuestDB IDE which web base does that. DBeaver Docker version is also web base and use JSON Also, I remember tables or easychart in Vision have same problem when the dataset is more than 1500 rows.

[image] nader.chinichian: But QuestDB IDE which web base does that. It is probably not converting everything to JSON, but delivering optimized HTML to directly populate the table. [image] nader.chinichian: tables or easychart in Vision have same problem when the dataset is more than 1500…

Is the Table virtualized turned on? Probably not for your use cases, but I find that that helps. Using paging as well...

I wonder how did you load millions of rows in Vision. One thing I saw every time a client loads something big like 3000 rows the RAM usage increases a lot and when the user closes the window the RAM doesn't decrease or decrease a little bit so eventually one day gateway crashes. how much Ignition's…

You have to chunk the queries. Vision can hold the chunks (and assemble into a full dataset) while the gateway lets them be garbage collected after transmission. Millions of rows in a dataset yields tens or a few hundreds of megabytes in client RAM, which is easily handled by client RAM configurat…

is this module only applicable to Vision?

You can use this module in Perspective, with expression bindings or scripting. It doesn't integrate with the Power Chart or normal history bindings (yet...). Be aware that using it in gateway scope will hold the gateway-side cache in place. Dataset fragments held by a Vision client (and no other …

I am trying to display a large amount of history data from Wonderware Historian in Perspective table and chart. is this a proper approach?

Is the Wonderware historian exposed as a normal SQL database connection? If so, I would expect it to work. This module does not act as a historian layer.

Perspective Table Performance Issue for Large Dataset

Ignition Early Access

bmusson August 20, 2026, 3:18am 17

You might want to check out this post for ideas: