![]() This means the server would page a hundred stacks to paint a hundred taskbar clocks.įor this particular reason, server admins usually disable ‘caret blinking’ to reduce CPU usage as caret blinking across a hundred users will contribute to CPU usage. In servers with multi-user support, the system will try to update the taskbar clock once a second for each user that signs in have their own taskbar clock. ![]() Let’s consider a configuration with multi-user support, like Terminal servers. While system memory is no longer the main concern as all devices now have a lot more than 4MB of memory, the frequent updates required for displaying seconds on the taskbar can still make your device slower than usual. ![]() So why not bring back the taskbar clock with seconds support? The reason is still performance, according to a new post on Microsoft’s dev blog. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |