On Improving Windows' Responsiveness


in previous life became familiar internal operating system algorithms. mainframe used called "time-sharing" machine. became obvious cannot serve dozens of logged on users equitably if rely on simple round-robin cpu dispatch scheme. vendor designed , implemented robust scheme ensured every user got slice of machine resources. no 1 user monopolize machine detriment of others. windows appears time slice round-robin scheme. pays no attention processes monopolize machine excessive i/o activity. that's when programs launch display not responding messages. aforementioned vendor apportioned time slices according standard units of processing doled out resources measured not cpu utilization by i/o utilization. perhaps in next round of windows changes, more attention paid such improvement, include giving boost user interested in seeing progress fastest evidenced clicking at, , less attention rearranging operating handles. example, new incantation finding control panel in windows 10?

mark d rockman


carey frisch changed type of item (i believe) question discussion. it's still question nobody, suppose, prepared answer.  still tantalizing question.  bone of contention:  item type represented icon definition, i'm asking, where?  how tool tip? 

mark d rockman



Windows 10 Insider Preview  >  Windows 10 Insider Preview Feedback



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS