4 ms·
Agreed, I have about 8GB of pages open right now not doing anything. Many computers don't have that much total ram. I think it's time to have per tab resource t
by RandyRanderson 10y ago
Agreed, I have about 8GB of pages open right now not doing anything. Many computers don't have that much total ram. I think it's time to have per tab resource throttling. For example if a page uses over a certain amount of
. compute resources, the cpu cycles allowed in the next epoch are halved
. RAM it's memory accesses per second are halved in the next epoch
. network traffic it's kB/s are halved in the next epoch
This would allow all pages to still work but the resource intensive ones would be flagged quickly by users and developers.
- warfangle 10y agoAnd immediately any webGL visualizations / games / necessarily resource intensive webapps are rendered useless as they're automatically throttled back by the browser.
- RandyRanderson 10y agoIt would be pretty easy to add a conspicuous button to "unlock" resources iff they were throttled. Being generous, I think the average user might actually push this btn once a month?