Hi everyone,
I’m currently working on a Constellation-based application in Pega Infinity, but I’ve been hitting some persistent performance issues that are starting to interfere with my development workflow, specifically within Dev Studio.
I am currently using a deltaexeutor community setup to handle some automated local logging and script execution on my workstation. I’ve noticed that whenever the background executor starts a heavy processing cycle, my Pega browser session becomes incredibly sluggish. I frequently experience “Page Unresponsive” errors when trying to save rules or open complex Data Transforms, and occasionally my session times out entirely, which is quite frustrating when I’m in the middle of a configuration.
It feels like the background process is competing for the same high-priority CPU threads and memory that the Pega UI engine needs for real-time rendering and secure socket communication. I have a few related concerns for the architects here:
I’m not sure if the way a deltaexeutor style environment manages its internal threading is causing a resource contention issue with the browser’s hardware acceleration or the specific Java runtime used by my local Pega instance. Has anyone else encountered performance bottlenecks or “Socket Timeout” errors while running high-level script executors alongside their Pega development environment? I am also wondering if there is a specific way to isolate the executor’s CPU priority so it doesn’t starve the resources I need for my Pega work, or if I should consider adjusting the memory heap settings for my local node.
I really need to keep this automation active while I build out my application, but the constant UI lag is making it difficult to maintain productivity. If anyone has experience optimizing a professional workstation for concurrent usage of heavy script executors and Pega’s development tools, I’d love to hear your advice!
Thanks!