Hello Distill Team,
I would like to suggest a feature that could significantly reduce memory and CPU usage for users monitoring websites such as YouTube.
Currently, Distill appears to rely heavily on browser-based page rendering and monitoring. While this works well, it can consume a noticeable amount of RAM when running many monitors at short intervals.
A colleague of mine has developed a monitoring system that performs most of its work on backend servers. Instead of relying on a browser to continuously load and inspect pages, the system distributes requests across many monitoring agents and rotates browser identities (user agents and request headers). This spreads the workload, reduces the chance of rate limits, and allows monitoring to be performed with very low client-side resource usage.
Potential benefits if Distill offered a similar lightweight monitoring mode:
-
Lower RAM usage.
-
Lower CPU usage.
-
Faster detection of updates.
-
Better scalability for users monitoring many channels or pages.
-
Reduced browser overhead.
Would it be possible for Distill to explore a backend-driven monitoring mode or other optimizations that reduce browser resource consumption while maintaining fast detection times?
Thank you for your time and for building a great monitoring tool.
Best regards,
A Distill User