5 ms·

The first reply on the top of that page is a classic "Isn't installing Spotify in a regular HDD an option?" Just completely ignore the problem and find a way

The first reply on the top of that page is a classic "Isn't installing Spotify in a regular HDD an option?" Just completely ignore the problem and find a way to let you pretend it doesn't exist.

croon 10y ago
Haha! I didn't even check, but that is indeed a very accurate synecdoche of their support forum at large. Good catch.
maccard 10y ago
After reading this thread, I'm actually going to do just that. Not that I agree with the solution but it solves my issue at least EDIT: Just tried to do so, and the spotify installer doesn't let you choose where to install.
- test1235 10y ago
  A typical response here would be, "Have you tried just switching out your main hard drive to a non-SSD and making that the default install location? Good luck!"
- mschulze 10y ago
  You can set the location of the cache in advanced settings IIRC.
  - mikeash 10y ago
    Thanks for pointing that out. Even ignoring the excessive writes, it'll be nice to have the cache take up space on my vast spinny drive rather than on my somewhat tight SSD.
    - cosmie 10y ago
      The folder isn't as large as the IO usage makes it out to be. The entire PersistentCache directory is only ~104MB on my drive, even with >300GB written in the last few days
      - mikeash 10y ago
        Good to know. I assumed it would not be dozens of GBs, but I assumed it might be one or two.
  - gaia 10y ago
    It is not the cache that causes the heavy IO. It is the SQLite DB at AppData\Local\Spotify\mercury.db AppData\Local\Spotify\mercury.db-wal See http://blog.scaleprocess.net/spotify-heavy-io-problem/ http://blog.scaleprocess.net/spotify-heavy-io-problem/ Besides that, a lot of times setting a diff location for your cache does NOT move the cache. I had to use a symlink.
- mdrzn 10y ago
  Also, they fixed this a couple months ago it seems. Page 22 of the comments in OP link.
  - maccard 10y ago
    I checked with some of my colleagues in work. My machine had 220GB written in 2 days. Another colleague had 300GB.
- cosmie 10y ago
  Go to Preferences -> Advanced Settings -> Change Cache Location It's the VACUUM'ing of the SQLite database in that folder that's the problem. Moving that destination to your other drive should hopefully move the IO with it (I don't have a second drive to test with)
raimue 10y ago
I think that often happens on support forums, because the power user volunteers trying to help others are too enthusiastic about the product. They have a deep bond to the product, that is strengthened by getting the (mental) reward of being recognized as an expert by answering a lot of questions on support forums. Therefore they will continue to use the product, even if it requires them to change their habits or to apply (costly) workarounds. Of course their answers will be written with this sentiment, so their suggestions might completely ignore the problem.

The first reply on the top of that page is a classic "Isn't installing Spotify in a regular HDD an option?" Just completely ignore the problem and find a way to let you pretend it doesn't exist.

croon 10y ago

Haha! I didn't even check, but that is indeed a very accurate synecdoche of their support forum at large. Good catch.

maccard 10y ago

After reading this thread, I'm actually going to do just that. Not that I agree with the solution but it solves my issue at least EDIT: Just tried to do so, and the spotify installer doesn't let you choose where to install.

test1235 10y ago
A typical response here would be, "Have you tried just switching out your main hard drive to a non-SSD and making that the default install location? Good luck!"
mschulze 10y ago
You can set the location of the cache in advanced settings IIRC.
- mikeash 10y ago
  Thanks for pointing that out. Even ignoring the excessive writes, it'll be nice to have the cache take up space on my vast spinny drive rather than on my somewhat tight SSD.
  - cosmie 10y ago
    The folder isn't as large as the IO usage makes it out to be. The entire PersistentCache directory is only ~104MB on my drive, even with >300GB written in the last few days
    - mikeash 10y ago
      Good to know. I assumed it would not be dozens of GBs, but I assumed it might be one or two.
- gaia 10y ago
  It is not the cache that causes the heavy IO. It is the SQLite DB at AppData\Local\Spotify\mercury.db AppData\Local\Spotify\mercury.db-wal See http://blog.scaleprocess.net/spotify-heavy-io-problem/ http://blog.scaleprocess.net/spotify-heavy-io-problem/ Besides that, a lot of times setting a diff location for your cache does NOT move the cache. I had to use a symlink.
mdrzn 10y ago
Also, they fixed this a couple months ago it seems. Page 22 of the comments in OP link.
- maccard 10y ago
  I checked with some of my colleagues in work. My machine had 220GB written in 2 days. Another colleague had 300GB.
cosmie 10y ago
Go to Preferences -> Advanced Settings -> Change Cache Location It's the VACUUM'ing of the SQLite database in that folder that's the problem. Moving that destination to your other drive should hopefully move the IO with it (I don't have a second drive to test with)

raimue 10y ago

I think that often happens on support forums, because the power user volunteers trying to help others are too enthusiastic about the product. They have a deep bond to the product, that is strengthened by getting the (mental) reward of being recognized as an expert by answering a lot of questions on support forums. Therefore they will continue to use the product, even if it requires them to change their habits or to apply (costly) workarounds. Of course their answers will be written with this sentiment, so their suggestions might completely ignore the problem.