Ian Morris writes in Forbes that the use of the Chrome browser on laptops with Windows can lead to a reduction of autonomy in Fort and 25%. This happens because the Chrome changes the "system clock tick rate to 1 millisecond instead of 15.6 milliseconds usually defined by Windows.
The tick rate is the default time for the processor "awaken" to check what is to be done. By default, in Windows the tick rate is marked for the 15.6 milliseconds, i.e. cefrca of 64 times per second.
In Internet Explorer, for example, the tick rate remains at 15.6 milliseconds, when you open the YouTube changes for 1 milliseconds and when it closes this separator, returns to 15.6 milliseconds. In Chrome, is always in 1 millisecond.
What this means in practice is that the processor wakes up about 1,000 times for every second to realize what has to be done, rather than being "only" 64 times per second.
Microsoft itself confirms that tick rates of 1 millisecond increases energy consumption by about 25%, writes Morris.
For now, there is no user-side solution to fix this solution. It is known that Google is analyzing the situation internally to provide a corrective update.
In Internet Explorer, for example, the tick rate remains at 15.6 milliseconds, when you open the YouTube changes for 1 milliseconds and when it closes this separator, returns to 15.6 milliseconds. In Chrome, is always in 1 millisecond.
What this means in practice is that the processor wakes up about 1,000 times for every second to realize what has to be done, rather than being "only" 64 times per second.
Microsoft itself confirms that tick rates of 1 millisecond increases energy consumption by about 25%, writes Morris.
For now, there is no user-side solution to fix this solution. It is known that Google is analyzing the situation internally to provide a corrective update.
No comments:
Post a Comment