So after we’ve extended the virtual cloud server twice, we’re at the max for the current configuration. And with this crazy growth (almost 12k users!!) even now the server is more and more reaching capacity.
Therefore I decided to order a dedicated server. Same one as used for mastodon.world.
So the bad news… we will need some downtime. Hopefully, not too much. I will prepare the new server, copy (rsync) stuff over, stop Lemmy, do last rsync and change the DNS. If all goes well it would take maybe 10 minutes downtime, 30 at most. (With mastodon.world it took 20 minutes, mainly because of a typo :-) )
For those who would like to donate, to cover server costs, you can do so at our OpenCollective or Patreon
Thanks!
Update The server was migrated. It took around 4 minutes downtime. For those who asked, it now uses a dedicated server with a AMD EPYC 7502P 32 Cores “Rome” CPU and 128GB RAM. Should be enough for now.
I will be tuning the database a bit, so that should give some extra seconds of downtime, but just refresh and it’s back. After that I’ll investigate further to the cause of the slow posting. Thanks @veroxii@lemmy.world for assisting with that.
Performance is looking awesome, lemmy.world is responding very fast to community subscription requests and search is also very fast. My experience when using other instances was that search didn’t work at all, hindering community discovery.
Thanks!
This is how I understand it: a current limitation (feature?) Is that you can only search from your instance to other communities if someone from your instance has interacted with it. But if you use https://browse.feddit.de/ you can search across all instances. Then subscribe to it, or search the whole url in your own instances search. Once an instance interacts with another, now other people from your instance can search for it by simple name.
So, mostly correct. Lemme clarify:
If you do a URL search in the communities page (with all settings set to “All”, even “Communities”), your instance will pull in a few of the latest posts and comments. Not anything too heavy, just enough to give you an idea of what’s going on.
The moment a single user on your instance subscribes, your instance will start pulling in everything from that community. If every instance pulled in every community from every other instance, the network would be very vulnerable to a botspam instance that goes up would crash everything. Much better for an instance to only pull in communities that people are interested in.
can the instance owner limit the rate of amount pulled? Say, if a malicious user joins a small server, and then subs every known nsfw instances’ communities what then? Like is lemmy by default a whitelist approach or blacklist? (or maybe somewhere in the middle?)
An instance owner decides. You can either make it whitelist or blacklist, your choice.
Oh, so it is due to the larger userbase here! There is a larger chance that someone already subscribed to a community I am looking for.
Still, when I was using another instance, subscribing to communities at lemmy.world was instantaneous while subbing to communities at beehaw.org or lemmy.ml often took more than one try.
It also doesn’t help that lemmy.ml where a lot of users migrated at first seems to be having issues right now.
Also on jerboa searching for communities by url doesn’t seem to be working.
Hopefully the influx of new users and attention helps improving and ironing some issues like it happened with mastodon.
This was exactly my issue. My feddit.uk instance was very slow. Couldn’t interact or search on Jerboa using URL. Lemmy.World instace is much better. Donation to the cause on the way.