Understood. I should mention that I am not discounting that AEON could be less than ideal in terms of its performance. There is at least one thread here addressing performance issues. But you and I are powerless to do anything about that. What we can do is give our machines a fighting chance to handle AEON better.
My writing project so far has 98 events, not many less than yours. I haven’t encountered any sort of latency in AEON. Since I built my machine for music production, where music samples are RAM-hungry, it has an admittedly ridiculous amount of RAM (128GB). That does not mean, of course, that 16 GB is insufficient RAM, though it doesn’t rule it out, either.
Regarding your paging file: If AEON is indeed hitting your paging file, which occurs of course when RAM is insufficient at that moment, that could account for the latency, particularly if your paging drive is not SSD.
As for the discrete graphics card, that’s of course helpful for graphics programs such as GIMP, but would that help for a data-driven program such as AEON? It seems to me (just guessing, honestly) that a lag in “rendering” is really a lag in processing the data per view, which is a CPU process rather than a graphics card process; it’s not “rendering” in the sense of rendering video or graphics programs such as GIMP, where yes, a graphics card will take on the task separate from the main CPU and thereby speed it along.
I hesitate to suggest buying more RAM since that costs money and time, but if it were me, I’d probably do it, for what it’s worth. I’d also consider adding an SSD, in case my laptop wasn’t already running an SSD. Now that I think about it, I’d probably start with the SSD drive and see if that solves it; a paging file working on an SSD drive rather than a mechanical drive is much faster. I did this with an older laptop a while back and it was startling how much better it performed. If that didn’t work, I’d boost the RAM to something like 32GB.
Hope this helps.