3 ms·
> don't have a proper way of prioritizing the user's needs To me that means it is no longer my/your computer. > Maybe there are experimental OS's which do thi
by 6510 6y ago
> don't have a proper way of prioritizing the user's needs
To me that means it is no longer my/your computer.
> Maybe there are experimental OS's which do this properly
https://en.wikipedia.org/wiki/RTLinux https://en.wikipedia.org/wiki/RTLinux
Funny: In JS I tried to find the maximum number of http requests a system could make. Async operations have unpredictable response time. Parsing the payload when it is returned was not an option since you end up with more parse jobs than the system can deal with at that moment which freezes the UI. (Earlier requests may arrive late, later requests might arrive soon.) So I ended up de-async-ing the tasks an doing them with setInterval (which requires checking the time or it will cluster up the parse tasks again) and tuning down the number of requests if there are many unfinished parse jobs. Now, if the user clicks something everything waits except dumping the responses into an array. Previously I couldn't lower the number of requests far enough to completely avoid UI freezes. They only got less frequent. With everything synced properly I can push the rate of the requests 20 times higher without freezes than async with 1 freeze per minute.