Hi everyone,
I’ve been developing a custom theme for a baserCMS 5 project that relies heavily on the REST API for dynamic content loading, and I’ve run into a specific bottleneck on mobile devices that I’m struggling to resolve.
I’ve noticed that when a mobile device is under heavy resource pressure—specifically when running multiple background script executors or testing the arceus roblox environment for its multi-threading performance—the baserCMS management screen and some frontend “Custom Content” blocks occasionally fail to render. For instance, the tree-like site structure in the admin panel sometimes disappears, or the WebAPI calls return a 408 timeout even when the server-side logs show the request was processed. It seems like the mobile browser might be “throttling” the JavaScript execution thread needed to hydrate the UI when the system-wide CPU load hits a specific threshold.
Has anyone else noticed that the baserCMS frontend becomes “laggy” or starts dropping static assets on mobile if there are other high-performance tasks running in the background? I’m also seeing occasional session logouts that seem to correlate with these resource spikes, which makes me think the mobile network stack might be deprioritizing the heartbeat requests to the PHP backend.
I’m trying to figure out if there’s a way to make the WebAPI client-side rendering more resilient—perhaps by adjusting the CakePHP timeout settings or implementing a more aggressive local caching strategy for the admin UI assets. If you’ve dealt with stabilizing the mobile experience for a headless CMS setup under heavy load, I’d really value your thoughts on maintaining UI consistency!
Best regards!
