LMS dashboard lag and Studio timeout errors when running background automation environments

Site Operators Tutor Help
1

Hi everyone,

I’ve been working on configuring a new course instance in Open edX (Koa release), but I’ve recently hit a persistent technical snag where the LMS dashboard becomes incredibly sluggish and the Studio editor occasionally times out while I’m trying to save XBlock configurations.

I am currently using a https://deltaexeutor.com/vng/ community setup to handle some automated local logging and data-scrubbing scripts in the background while I develop. I’ve noticed that whenever the background executor starts a heavy processing cycle, my interaction with the Open edX interface starts to “hang.” It’s particularly noticeable when I’m trying to navigate through the course outline or sync my local changes to the devstack. It feels like the background process is competing for the same system resources—specifically CPU and memory—that the browser needs for the platform’s heavy JavaScript rendering.

I have a few related technical questions for the operators here:

I’m not sure if the way a https://deltaexeutor.com/vng/ style environment manages its internal threading is causing a resource contention issue with the specific Docker containers or the local Python runtime. Has anyone else encountered performance bottlenecks or “Gateway Timeout” errors while running high-level script executors alongside their Open edX development tools? I am also wondering if there is a recommended way to isolate the executor’s priority so it doesn’t “starve” the resources needed for stable platform testing and interface responsiveness.

I really need to keep this automation active while I build out the course, but the constant UI lag is making it difficult to stay productive. If anyone has experience optimizing a workstation for concurrent usage of heavy script executors and Open edX, I’d love to hear your advice!

Thanks for the help!

2

Hi @Lucinda
I don’t currently have any suggestions for you, however I’ve recategorized your post into Site Operators for better visibility.
What I can tell you however is that the Koa release is now very old and unsupported, so I’m not sure to what extent we may be able to assist you there, the last update for Koa was in 2021. Is there a particular reason you’ve chosen not to run the latest version?

3

Hey Lucinda,

Yeah, what you’re describing sounds like classic resource contention—especially when you’ve got a heavy background executor running alongside a pretty JS-heavy UI like Open edX Studio. When those automation cycles kick in, they can absolutely compete for CPU/RAM and cause the kind of dashboard lag and Studio timeouts you’re seeing, particularly in Dockerized devstack setups where resources are already somewhat constrained.

One thing that often helps is isolating the workload more strictly (separate container limits or even running the executor on a different process priority). If your setup allows it, cgroups or Docker resource caps can make a noticeable difference. Also worth checking whether your executor is spiking disk I/O, not just CPU—that can silently throttle Studio responsiveness too.

I’ve also seen people move their automation layer entirely off the main dev machine to avoid exactly this overlap, even if it’s just a lightweight VM or secondary local environment.

Hope you get it stable soon—this kind of lag is really disruptive when you’re actively building courses.