<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Timer Resolution in Desktop (Windows)</title>
    <link>https://community.spotify.com/t5/Desktop-Windows/Timer-Resolution/m-p/4372608#M51983</link>
    <description>&lt;P&gt;Is there a reason why Spotify overrides the default system timer resolution of 15.6ms and requests a 1ms timer? This seems pretty excessive for any reasonable use case and is going to be a battery hog.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Running 'powercfg.exe /energy' yields this in the report:&lt;/P&gt;&lt;DIV class="log-entry-header"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="log-entry-header"&gt;Platform Timer Resolution:Outstanding Timer Request&lt;/DIV&gt;&lt;DIV class="log-entry-content"&gt;&lt;DIV class="log-entry-description"&gt;A program or service has requested a timer resolution smaller than the platform maximum timer resolution.&lt;/DIV&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN class="detail-name"&gt;Requested Period&lt;/SPAN&gt;&lt;/TD&gt;&lt;TD&gt;10000&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN class="detail-name"&gt;Requesting Process ID&lt;/SPAN&gt;&lt;/TD&gt;&lt;TD&gt;4236&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN class="detail-name"&gt;Requesting Process Path&lt;/SPAN&gt;&lt;/TD&gt;&lt;TD&gt;\Device\HarddiskVolume4\Program Files\WindowsApps\SpotifyAB.SpotifyMusic_1.72.117.0_x86__zpdnekdrzrea0\Spotify.exe&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is without Spotify playing, btw, it's just loaded. Windows 10 build 16299.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Those of us on battery power would appreciate it if someone could take a look &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 29 Jan 2018 23:37:39 GMT</pubDate>
    <dc:creator>Astrion</dc:creator>
    <dc:date>2018-01-29T23:37:39Z</dc:date>
    <item>
      <title>Timer Resolution</title>
      <link>https://community.spotify.com/t5/Desktop-Windows/Timer-Resolution/m-p/4372608#M51983</link>
      <description>&lt;P&gt;Is there a reason why Spotify overrides the default system timer resolution of 15.6ms and requests a 1ms timer? This seems pretty excessive for any reasonable use case and is going to be a battery hog.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Running 'powercfg.exe /energy' yields this in the report:&lt;/P&gt;&lt;DIV class="log-entry-header"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="log-entry-header"&gt;Platform Timer Resolution:Outstanding Timer Request&lt;/DIV&gt;&lt;DIV class="log-entry-content"&gt;&lt;DIV class="log-entry-description"&gt;A program or service has requested a timer resolution smaller than the platform maximum timer resolution.&lt;/DIV&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN class="detail-name"&gt;Requested Period&lt;/SPAN&gt;&lt;/TD&gt;&lt;TD&gt;10000&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN class="detail-name"&gt;Requesting Process ID&lt;/SPAN&gt;&lt;/TD&gt;&lt;TD&gt;4236&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN class="detail-name"&gt;Requesting Process Path&lt;/SPAN&gt;&lt;/TD&gt;&lt;TD&gt;\Device\HarddiskVolume4\Program Files\WindowsApps\SpotifyAB.SpotifyMusic_1.72.117.0_x86__zpdnekdrzrea0\Spotify.exe&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is without Spotify playing, btw, it's just loaded. Windows 10 build 16299.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Those of us on battery power would appreciate it if someone could take a look &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2018 23:37:39 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Desktop-Windows/Timer-Resolution/m-p/4372608#M51983</guid>
      <dc:creator>Astrion</dc:creator>
      <dc:date>2018-01-29T23:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: Timer Resolution</title>
      <link>https://community.spotify.com/t5/Desktop-Windows/Timer-Resolution/m-p/4454694#M57028</link>
      <description>&lt;P&gt;I noticed this issue happening with the Web Player version of Spotify on Firefox versions 54-56 as well.&amp;nbsp; There is no reason that Spotify needs that level of granularity for audio processing.&amp;nbsp; The default 15.6ms is more than enough to properly buffer and playback audio.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Apr 2018 18:42:54 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Desktop-Windows/Timer-Resolution/m-p/4454694#M57028</guid>
      <dc:creator>djkanoko</dc:creator>
      <dc:date>2018-04-16T18:42:54Z</dc:date>
    </item>
    <item>
      <title>Re: Timer Resolution</title>
      <link>https://community.spotify.com/t5/Desktop-Windows/Timer-Resolution/m-p/4988880#M88149</link>
      <description>&lt;P&gt;This is still an issue with Spotify today. Here's a relevant blog post about this class of problem:&amp;nbsp;&lt;A href="https://randomascii.wordpress.com/2013/07/08/windows-timer-resolution-megawatts-wasted/" target="_blank" rel="noopener"&gt;https://randomascii.wordpress.com/2013/07/08/windows-timer-resolution-megawatts-wasted/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's just poor programming, and there's no excuse for wasting battery power for those of us using laptops.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some context from&amp;nbsp;&lt;A href="https://docs.microsoft.com/en-us/windows/win32/api/timeapi/nf-timeapi-timebeginperiod" target="_blank"&gt;https://docs.microsoft.com/en-us/windows/win32/api/timeapi/nf-timeapi-timebeginperiod&lt;/A&gt;:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;This function affects a global Windows setting. Windows uses the lowest value (that is, highest resolution) requested by any process. Setting a higher resolution can improve the accuracy of time-out intervals in wait functions. &lt;STRONG&gt;However, it can also reduce overall system performance, because the thread scheduler switches tasks more often. High resolutions can also prevent the CPU power management system from entering power-saving modes.&lt;/STRONG&gt; Setting a higher resolution does not improve the accuracy of the high-resolution performance counter.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2020 10:36:13 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Desktop-Windows/Timer-Resolution/m-p/4988880#M88149</guid>
      <dc:creator>Astrion</dc:creator>
      <dc:date>2020-07-02T10:36:13Z</dc:date>
    </item>
  </channel>
</rss>

