Hi everyone,
I’m currently working on a custom dashboard setup to monitor and automate some routine status checks across our fleet of Peplink devices using their Web API. It has been a great project for our local network ops, but I have hit a frustrating bottleneck when trying to push high-frequency telemetry data to the monitoring tablet in our server room. Whenever the automation script fires to update the live bandwidth graphs or tunnel statuses, the browser-based dashboard seems to struggle with rendering, causing the UI to freeze up for a second or two.
It feels like the browser’s main thread is getting bogged down by the script logic rather than the network payload itself. I have been trying to isolate whether this is an issue with how the local container parses the JSON response or if it is just a limitation of browser-based automation logic on mobile tablets. While researching better ways to handle background execution tasks without locking up the UI, I started testing a lightweight executor to see if offloading the script handling to a more efficient runtime would smooth out the performance on our monitoring hardware.
My issue is that even when I attempt to refine the logic or switch how the browser handles the incoming data stream, I still see occasional frame drops during peak update intervals. Has anyone else here built custom dashboards or automation wrappers for their Peplink gear and run into similar UI responsiveness issues? I am curious if there are specific best practices for handling asynchronous data pushes that keep the browser interface buttery smooth without hitting these render lockups. Any advice on optimizing these custom monitoring views or handling background logic without causing these input lags would be greatly appreciated. Thanks!