I am using gSender 1.5.3 on a gControl computer with upgraded memory.
I have had occasion to run many (letās say more than 50) short .nc files today. I noticed a distinct slowing down of the loading process on gSender as more and more individual tool path files are loaded. Things start out snappy with the files being on a local USB stick. There are only 9 files total but I load one tool path, then the next tool path before re-loading tool path number one. There may be two or up to 4 tool paths to process one piece of stock.
Anyway, there is a distinct slow down for loading files - the loading starts out almost instantaneously (small files) and as more and more files are loaded and re-loaded things slow down. I eventually had to re-boot the gControl computer as it got to a point where a file that loaded almost instantaneously ended up taking more than 30 seconds before it finished the loading. It felt like it took longer to load a file than to actually run the file.
Anyway, there is something hinky going on with memory management. While it might not be obvious right after booting the gControl, it eventually becomes a serious problem.
@Jens Might be worthwhile to check and note down the resources with Task Manager as it gets worse.
With gSender being idle since last night, CPU usage from gSender fluctuates between 80 and 95%. Memory usage is 650 Mb.
Note that when last used 8-10 hrs earlier, the response from gSender was still acceptable.
After a system reboot, gSenger uses around 9% of the CPU resources and around 585 Mb of memory
The memory seems fine, at least the two times you checked it, but hogging the whole CPU isnāt good.
Might be worth looking for a program that can record system data over time.
This is probably overkill and more than you want to get into but Iāve use Prometheus and Grafana, the OSS edition not the cloud, to monitor my media server (old PC), my PC and raspberry piās before. I used them for a couple of months to make sure the i5 2600 was enough for my server.
It was overkill for my needs and there must be a simpler solution if you only want to get data for a one PC. It was fun to examine all that data though.
Yes, I agree that memory is fine. Itās only around 20% of the total available.
I checked again after having rebooted earlier and after running a whole bunch of .nc files - gSender was consuming around 90% (total CPU utilization hovered around 100%)
This time around I closed gSender but did not reboot the gControl computer. After gSender was up and running, CPU usage was back to normal.
I am not going to dive into the reasons why this is happening. My participation is limited to reporting the issue. Sienci has people that live and breath gSender. They are much more qualified to look at things.
jumping in here to say Iāve noticed slowdowns just with gSender idling. I run it on a raspberry pi 5 and while that doesnāt give it a whole lot of headroom, itās pretty okay when I first load it up, but over the course of a night or two it gets more and more sluggish if I just leave it on.
Scrolling in the settings panel gets bad especially quickly.
@Jens @pmcquay thanks for both your notes on this. @KGN can speak more to this, but in the process of chasing down a different report a couple days ago, he stumbled upon a memory leak in the visualizer mostly related to how lightweight mode is handled and there being multiple instances of data being created and not destroyed. Not sure if this aligns exactly to what youāve reported seeing here, but there have been some changes made to the upcoming 1.6.0 build to address what was found so perhaps once it releases if you get the chance you could try again and let us know if youāre seeing any improvement on your end 
works for me, Iāve not been using lightweight mode, but its possible the changes made a difference.