# Ignition edge trend slow **URL:** \ **Category:** Ignition\ **Created:** [June 13, 2025, 7:18am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359 "2025-06-13T07:18:38Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![fe\_sha](https://avatars.discourse-cdn.com/v4/letter/f/a88e57/32.png) [@fe\_sha](https://forum.inductiveautomation.com/u/fe_sha)\ **Post date:** [June 13, 2025, 7:18am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/1 "2025-06-13T07:18:38Z")
We have purchased some touch panel and make it to “best performance”. As ignition edge doesn’t have db capacity, we only can connect to default Edge historian. I have created one screen for power chart and one screen for table to populate the historical data. The response is very slow. How can we improve it? ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [June 13, 2025, 7:22am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/2 "2025-06-13T07:22:18Z")
What hardware specifications are you running it on? ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [June 13, 2025, 11:43am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/3 "2025-06-13T11:43:48Z")
In addition to what @David_Stone asked, how much data are you retrieving? Both in terms of length of time and number of tags in the query/trend. ---
**Author:** ![fe\_sha](https://avatars.discourse-cdn.com/v4/letter/f/a88e57/32.png) [@fe\_sha](https://forum.inductiveautomation.com/u/fe_sha)\ **Post date:** [June 16, 2025, 2:16pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/4 "2025-06-16T14:16:38Z")
for the Data Table. I have retrieved 27 column,1min periodic query for 7 days. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/a/aa5ca2b317bed99eb852168fe124b4cdfb50724b.png) for the Trend, above 50 tag to be log into Edge Historian. but in default, 13 tags and 1 hour has been populate when navigate to the trend view. my Touch Panel hardware specification as below: Processor: Intel Celeron CPU N3060 1.60GHz RAM: 8GB The entire ignition client is not very smooth. any advise for this hardware spec? ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [June 16, 2025, 9:43pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/5 "2025-06-16T21:43:10Z")
> [@fe\_sha](#): > > my Touch Panel hardware specification as below: > Processor: Intel Celeron CPU N3060 1.60GHz > RAM: 8GB Are you running windows? If so, first way to optimise this is to use something other than windows that doesn't kill the performance of your hardware. This processor is not suitable for smooth trending, you will display things OK on the screen, but because browsers only render in single threaded configuration, the processor on this will never be good enough for snappy smooth rendering. To give you perspective, rendering trends on a raspberry pi 4 is similar to this, and its not brilliant, the upside is it doesn't use windows, so it is better at using all available hardware resources. Raspberry pi 5 is fast enough to run things much more acceptably. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [June 16, 2025, 9:46pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/6 "2025-06-16T21:46:51Z")
Make sure you're only retrieving what you need and nothing more (Do you really need all 7 days displayed?). The current query is retrieving 10,442 rows. Since you're using Min/Max, you might also change that to something else as I believe for reporting in a table it will return 2 records for every minute - doubling your data due to one record for min and another for max. ---
**Author:** ![fe\_sha](https://avatars.discourse-cdn.com/v4/letter/f/a88e57/32.png) [@fe\_sha](https://forum.inductiveautomation.com/u/fe_sha)\ **Post date:** [June 17, 2025, 2:03am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/7 "2025-06-17T02:03:13Z")
So can i say upgrade the CPU will be the ideal solution? I can run smooth using my own laptop. But when things come to Touch Panel. it is bad not only the trend/data table but also for entire application. ---
**Author:** ![fe\_sha](https://avatars.discourse-cdn.com/v4/letter/f/a88e57/32.png) [@fe\_sha](https://forum.inductiveautomation.com/u/fe_sha)\ **Post date:** [June 17, 2025, 2:07am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/8 "2025-06-17T02:07:44Z")
Actually customer need longer period, I have convinced them to 7 days. They need to export the data to csv for further analysis. Any advise for the default aggregation mode? i dont want 2 record in a single minute. Something like this: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/9/b9019e7608c8dd72fe041e5fc3bf5c437767b378.png) ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [June 17, 2025, 2:15am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/9 "2025-06-17T02:15:24Z")
If that's the data you're getting, then it's fine. You probably need a higher powered computer to run this on to pull that much data and export to CSV or excel though. ---
**Author:** ![fe\_sha](https://avatars.discourse-cdn.com/v4/letter/f/a88e57/32.png) [@fe\_sha](https://forum.inductiveautomation.com/u/fe_sha)\ **Post date:** [June 17, 2025, 2:55am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/10 "2025-06-17T02:55:45Z")
Do we have any documentation regarding hardware recommendation in ignition website? Now my entire ignition application is not smooth enough.(not only trend/data table view) ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [June 17, 2025, 3:15am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/11 "2025-06-17T03:15:12Z")
Have you looked at your CPU and memory usage on that PC? As others have mentioned, Linux will use less resources for the OS, so can give better performance as well. Have you edited the ignition.conf file to increase the initial and maximum memory to give the application more memory to work with? > **[Gateway Configuration File Reference | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/appendix/reference-pages/gateway-configuration-file-reference)** > > This section details the various configuration changes that can be made to the Gateway's configuration file: ignition.conf. Before the Gateway starts, a wrapper service checks the configuration file for parameter values, and then attempts to start... ---
**Author:** ![fe\_sha](https://avatars.discourse-cdn.com/v4/letter/f/a88e57/32.png) [@fe\_sha](https://forum.inductiveautomation.com/u/fe_sha)\ **Post date:** [June 17, 2025, 8:42am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/12 "2025-06-17T08:42:29Z")
I just checked the performance on gateway. Our memory allocation is 2048, and the memory trend never hit 1000. I believe that our processor is not good enough to run ignition. When we run ignition, the CPU alway shoot to 100%. It only back to normal (\<40%) when we stop the ignition gateway and shoot up again when we start gateway. ![Image (1)](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/d/2d296681c5f2d1bfcda68a0b0a214d1aa6df1d95.jpeg) Below is the panel datasheet we used for our project. [got5103w-845.pdf](https://www.axiomtek.com.tw/Download/Spec/en-US/got5103w-845.pdf) ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [June 17, 2025, 11:11am UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/13 "2025-06-17T11:11:12Z")
I would still increase the memory allocation in the ignition.conf file, but that CPU is definitely underpowered. It only has 2 cores. You'll want a more modern processor that's both faster (avoid Celeron) and has more cores. Unfortunately that means buying an entirely new PC as you can't just upgrade the one you have. > **[UserBenchmark: Intel Celeron N3060 vs Pentium N3710](https://cpu.userbenchmark.com/Compare/Intel-Pentium-N3710-vs-Intel-Celeron-N3060/m141841vsm130019)** > > Based on 32,927 user benchmarks for the Intel Celeron N3060 and the Pentium N3710, we rank them both on effective speed and value for money against the best 1,406 CPUs. While you could try the Pentium N3710 model, as you can see from the link, it's faster but still a 9 year old processor. ---
**Author:** ![fe\_sha](https://avatars.discourse-cdn.com/v4/letter/f/a88e57/32.png) [@fe\_sha](https://forum.inductiveautomation.com/u/fe_sha)\ **Post date:** [June 17, 2025, 1:57pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/14 "2025-06-17T13:57:23Z")
Understand that replace the hardware will be the simplest solution. Just to check if we reduce the tag to log into Edge historian? Is it possible to improve the performance? ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [June 17, 2025, 8:31pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-trend-slow/107359/15 "2025-06-17T20:31:58Z")
I’m pretty sure it’s the rendering that’s killing it not the historical tags.