this post was submitted on 01 Jul 2023
3683 points (97.1% liked)

Lemmy.World Announcements

29077 readers
136 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages πŸ”₯

https://status.lemmy.world/

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

Donations πŸ’—

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
 

Looks like it works.

Edit still see some performance issues. Needs more troubleshooting

Update: Registrations re-opened We encountered a bug where people could not log in, see https://github.com/LemmyNet/lemmy/issues/3422#issuecomment-1616112264 . As a workaround we opened registrations.

Thanks

First of all, I would like to thank the Lemmy.world team and the 2 admins of other servers @stanford@discuss.as200950.com and @sunaurus@lemm.ee for their help! We did some thorough troubleshooting to get this working!

The upgrade

The upgrade itself isn't too hard. Create a backup, and then change the image names in the docker-compose.yml and restart.

But, like the first 2 tries, after a few minutes the site started getting slow until it stopped responding. Then the troubleshooting started.

The solutions

What I had noticed previously, is that the lemmy container could reach around 1500% CPU usage, above that the site got slow. Which is weird, because the server has 64 threads, so 6400% should be the max. So we tried what @sunaurus@lemm.ee had suggested before: we created extra lemmy containers to spread the load. (And extra lemmy-ui containers). And used nginx to load balance between them.

Et voilΓ . That seems to work.

Also, as suggested by him, we start the lemmy containers with the scheduler disabled, and have 1 extra lemmy running with the scheduler enabled, unused for other stuff.

There will be room for improvement, and probably new bugs, but we're very happy lemmy.world is now at 0.18.1-rc. This fixes a lot of bugs.

(page 4) 50 comments
sorted by: hot top controversial new old
[–] WeAllShineOn97@lemmy.world 5 points 1 year ago (1 children)

My first comment on here! Thanks for creating this, this looks fantastic and a great Reddit alternative. Keep up the great work.

load more comments (1 replies)
[–] sigh@lemmy.world 5 points 1 year ago

Fuck yeah upgrade hype

[–] decadentrebel@lemmy.world 5 points 1 year ago

Special thanks to the other guys for helping make this update possible. Site is snappier than ever and the UI looks fantastic.

[–] itadakimasu@lemmy.world 5 points 1 year ago

Thank you! I love it here. Sending good vibes

[–] Mishaye@lemmy.world 5 points 1 year ago

Thanks! Seems to be working fine so far.

[–] Grangle1@lemmy.world 5 points 1 year ago

Login problem is fixed for me, yay! Back on Jerboa and here on the browser! Thanks for your hard work and for putting up with me, lol.

I'm getting network errors that aren't allowing me to actually view content on Jerboa right now, though, but at this point I'm assuming it's a Jerboa thing and not a problem with the instance.

[–] BitOneZero@lemmy.world 5 points 1 year ago (1 children)

Edit still see some performance issues. Needs more troubleshooting

Federation overheard is putting a lot of load on servers. Creating one task for every single post, comment, and vote in RAM-only queue.... pending changes: https://github.com/LemmyNet/lemmy/pull/3466

load more comments (1 replies)
[–] Anaralah_Belore223@lemmy.world 5 points 1 year ago* (last edited 1 year ago)

The update is good. Just needs more troubleshooting

Trying to edit this comment

Editing took between 4 to 11 seconds. on https://lemmy.world/c/lemmyworld

Meanwhile, on other communities... 0.5 to 1 seconds

[–] yuki2501@lemmy.world 5 points 1 year ago

Thanks! Now I can use Connectβ„’ for Lemmy without problems. πŸ‘πŸ™‚

[–] 2014MU69@lemmy.world 5 points 1 year ago* (last edited 1 year ago) (6 children)

I am still getting errors half the time I do anything while using jerboa

Website is working great though

Edit: It's suddenly working a lot better now. Hopefully I am not jinxing myself.

[–] lemann@lemmy.one 5 points 1 year ago (3 children)

You running the latest Jerboa version?

If you can no longer see your subscribed communities in the sidebar, you could be on an older version that doesn't fully support v0.18.x

load more comments (3 replies)
load more comments (5 replies)
[–] itsnotlupus@lemmy.world 4 points 1 year ago

I like it.
The site feels a lot better to me, and seems significantly gentler in terms of browser resource consumption.

[–] solidgrue@lemmy.world 4 points 1 year ago

Its been pretty snappy for me all afternoon! No errors to speak of.

Nice work!

[–] BURN@lemmy.world 4 points 1 year ago

This looks like it’s exposed some weaknesses, and it sounds like the team has it under control.

I’m moving right now and can’t dedicate time to development, but once I’m up and running I should be able to start contributing.

Scalability is always a concern with these sites, so there’s plenty to do to improve that

[–] albertye@lemmy.world 4 points 1 year ago* (last edited 1 year ago) (1 children)

I can't login from my main browser even if I clear the cache and cookies, if I use other browser it works

Edit: I fixed it just by changing my browser language to English and restarting it, hope this is useful for someone.

Also, thanks to Ruud and team for the hard work, everything seems to work really well and fast.

load more comments (1 replies)
[–] danielfh@lemmy.world 4 points 1 year ago

Thank you!!

[–] Rooki@lemmy.world 4 points 1 year ago (1 children)

Is there a issue with the api? ( Because the api wrapper lemmy-js-client doesnt work on login. ) I tried it yesterday but not today yet. I will test it when i can :)

load more comments (1 replies)
[–] Bushwhack@lemmy.world 4 points 1 year ago

I survived!

[–] guyman@lemmy.world 4 points 1 year ago

Lot of network errors, but it could be jerboa.

[–] FollyDolly@lemmy.world 4 points 1 year ago

We're back baby!

[–] EmielBlom@lemm.ee 4 points 1 year ago (2 children)

Nice, really liking the update! Some questions about development for the fediverse: Is the code for running Lemmy written by one or person or a smome core team?

Is there any decision making process as to which features will be worked on in the next release or which bugs to prioritize?

In theory what would happen if the original developers started making changes that other people don't agree with? Would we get a fork then where servers have to choose to adopt it or not?

load more comments (2 replies)
[–] klp@lemmy.world 4 points 1 year ago

Thanks for the update. I especially like the transparency on not only the β€œupgrade” itself but also the potential issues encountered, together with the solutions. Seems rare nowadays, or I’m just seeing less and less people doing this.

[–] matt@lemmy.world 4 points 1 year ago

Also chipping in to give my appreciation, really enjoying Lemmy through lemmy.world!

[–] cute_cat@lemmy.world 4 points 1 year ago

I really enjoy how lemmy is growing!

[–] stickyfranklin@lemmy.world 4 points 1 year ago
[–] Panda@lemmy.world 4 points 1 year ago

Thanks so much for everything!

[–] cute_cat@lemmy.world 4 points 1 year ago

I really enjoy how lemmy is growing!

[–] nico@r.dcotta.eu 4 points 1 year ago* (last edited 1 year ago) (1 children)

Have you considered running your Lemmy instance on more than a single machine? If it is possible to run two lemmy containers anyway (ie, lemmy is not a singleton), why not run them on separate machines? With load balancing you could achieve a more stable experience. It might be cheaper to have many mediocre machines rather than a single powerful one too, as well as more sustainable long-term (vertical vs horizontal scaling).

The downside would be that the set-up would be less obvious than with Docker compose and you would probably need to get into k8s/k3s/nomad territory in order to orchestrate a proper fleet.

load more comments (1 replies)
[–] MicahParsons@lemmy.world 4 points 1 year ago

This is really cool that this gets shared. Thanks for all of the info!

[–] DelvianSeek@lemmy.world 4 points 1 year ago

Just want to say thank you. Your hard work is very much appreciated.

load more comments
view more: β€Ή prev next β€Ί