Saturday, April 19, 2003
I didn't really know how important the wishlist feature was to users until I read the thread on the messageboard, since I myself have had a grand total of two entries on my wishlist in the last year. Here's what I'm doing now instead: I increased the maximum number of entries on the wishlist from 5 to 40. So far the server seems to be handling that fine, but if things start slowing down, I'm gonna turn search skipping on for wishlist entries, which would mean a certain percentage of all users, roughly 25%, will receive each wishlist entry (randomly picked users each time) instead of everyone. The CPU upgrade we tried a couple of weeks ago didn't go well, only half the memory was recognized, so we had to roll back. I talked to CIFNet and they're about to get suitable memory, so I hope we'll be able to move to that P4 soon.
Nir 4:53 PM
Friday, April 18, 2003
Starting today, the server will only accept up to five wishlist entries from each person. Some of you have been overusing the feature to the point where the server would repeatedly choke, disconnect users, throw away packets, etc etc. Alexbk, python soulseek's developer, offered the idea that we separate regular searches from wishlist searches in such a way that regular searches would be distributed to everyone, while only a certain percentage would receive each wishlist search. That gave us all the breathing room we needed but was also penalizing users who were using the wishlist to find two or three things they were badly looking for at the expense of those who took to individually input each track name of every album they were looking for to their wishlists.
Nir 2:51 PM
Thursday, April 17, 2003
Posted 146c to the website. It fixes the much reported problem of new uploads not getting started if there are downloads coming from the same user. Also fixed a minor bug to slightly reduce bandwidth consumption on file transfer negotiation.
Nir 4:52 PM
Soulseek is broken. Please come back tomorrow.
Nir 2:30 AM
Monday, April 14, 2003
If you've suspected the announcement made on the old server about the availability of client v. 145 brought the server to its knees in a mad rush of downloads, you were right on the money. I temporarily shut the old server down to help the HTTP daemon out, but the whole system is running without a single CPU cycle to spare, so it's gonna be hairy for a short while. If you can't log on or download the new client, you should probably give up and come back in a few hours. Things should be much better then.
Nir 10:53 AM
Sunday, April 13, 2003
The main server's been maxing the CPU out for a few days and there's a really good chance the distributed network changes in the test version will help with that, so I repackaged test 11 and posted it to the homepage as client version 145. This will log on to what was formerly the test server, but if for any reason you decide you want to go back to the old client and server after you've upgraded, I also kept a link to 139c on the download page. Just make sure to let the installer overwrite the newer files when it asks.
Nir 10:17 PM