Is the wishlist feature now premium?

[thegroov...@gmail.com]

Hey,

I reinstalled SoulseekQT from scratch in September and added quite a few wishlist searches at the time (approx. 150). During the first days I was receiving plenty notifications just as before (several every day). Then, over time, I began to receive less and less alerts. By mid-November I wasn't receiving ANY notification any longer.

Last week a friend of mine sent me 15 days of privileges as a gift and I immediately started receiving alerts again... by the dozens! Since last week at least 25 notifications pop-up every day! Some I know I added back in September...

Why is my wishlist feature only working when the privileges are enabled? Will it turn off again when my premium days are gone?

I have no other search related issue, my ports are open, my downloads/uploads speed are fast and I can browse users without any problem.

As I already reported a while ago, Soulseek is however still super sluggish, constantly lagging and over consuming CPU and RAM if I dare leaving the application open without rebooting every two hours even on my new high end 2017 iMac...

Thanks in advance for the help.

Using 2017.11.21 build on macOS 10.12.6 (Sierra), iMac 2017

[Nir Arbel]

Hey grooveselector,

Regarding the performance issues, I wonder if it has something to do with having a lot of wishlist searches and/or receiving a lot of search results. Do you typically have a lot of search result windows or browsed share windows open when you observe high memory/CPU consumption?

Wishlist searches are still processed when you don't have privileges, albeit much more slowly to avoid saturating the distributed search network.

[thegroov...@gmail.com]

Hey Nir,

Thanks for your prompt answer!

My performance issues definitely have something to do with the (wishlist) search/chat windows. The more I have open, the more the application reacts slowly and memory/CPU consumption increases. I usually reboot soulseek as soon as I have more than 10-20 (wishlist) search/chat tabs total open simultaneously. I figured it's faster than closing them manually. The application never crashes, however after a few hours without rebooting any interaction gets reaaalllyyy slooowwwwwwww (every click on a search tab or chat tab makes between 2 and 15sec to register and omnipresent spinning wheel makes any chat conversation a nightmare. All these issues vanish as soon as I reboot the app.

Regarding the wishlist process: I now understand why it works better with privileges. However, I had not received a single wishlist notification for the last 10days prior to the activation of my privileges so I'm still confused whether it works at all without privileges on my end. However I do have a lot more wishlist searches now than before - approximately 400-500 at the moment. Would that be reason for the server not to processing my wishlist searches with no privilege enabled?

Your help is greatly appreciated. Your little blue bird has been part of my musical journey for more than 10 years now :)

[Nir Arbel]

No problem! Here's where it gets a little involved. To start with, how much of your system memory is taken up by that point?

The client uses a data management system that's really great at organizing complex data in a useful way, but is definitely on the wasteful side when it comes to memory. If I were to seriously address memory consumption issues, I'd engineer it completely out of three areas of function: searches, sharing of your own files, and browsing other users' shares. Browsing a really large share can easily cost hundreds of megabytes. Searches are more conservative because they're limited to 10,000 results for each window. But I guess those add up too if you have a lot of them open. Sharing a lot of files is pretty much the same memory-wise as browsing a lot of files. 

Replacing said data management system with native containers is a *big* refactor, so I want to make sure we're not barking up the wrong tree in this case. I'm not sure the memory and CPU consumption are related. One thing you could try is run a search, then browse the shares of users you're getting results from and try to get to a point where it very quickly consumes about the same amount of memory as it does after a few hours of receiving wishlist search results, and see if that affects CPU consumption.

Either way, I'll seriously consider trying to engineer the data management system out of search results over the next week to start with. If I do it's bound to take anywhere from a few days to a couple of weeks.

Cheers, Nir

[Nir Arbel]

Regarding wishlist searches: regardless of whether you have privileges or not the client cycles through your list of wishlist searches and sends them one at a time, every so often. Without privileges, it's limited to only sending a few each hour. With, it's every few minutes. I have to imagine that it probably takes it a *very* long time to cycle through such a big list without privileges, so it might just be a matter of not getting to the right users with the right search in time. Whenever you restart the client, it starts from the beginning of the list so it might never actually get to the parts that return any results, especially if you restart it every few hours as you describe.