2 ms·
I think the vast majority of the time unresponsive GUI are because of blocking network or IO calls. A faster CPU won't do anything. I rarely max out my CPU.
by cm2187 9y ago
I think the vast majority of the time unresponsive GUI are because of blocking network or IO calls. A faster CPU won't do anything. I rarely max out my CPU.
- 14113 9y agoA UI shouldn't be unresponsive in that case. It should present a progress bar, or other visual indicator that the UI [thread/actor/process] is waiting for the IO [thread/actor/process]. A UI should only become unresponsive when only one [thread/actor/process] is trying to do everything (I.e. both IO and UI), which should only occur if your application is not written with concurrency in mind.