this post was submitted on 04 Jul 2023

994 points (99.1% liked)

Lemmy.World Announcements

29104 readers

3 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 [email protected] e-mail.

Report contact

DM https://lemmy.world/u/lwreport
Email [email protected] (PGP Supported)

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

Join the team

founded 2 years ago

MODERATORS

[email protected]

994

Lemmy.world status update 2023-07-04 (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

170 comments fedilink hide all child comments

Status update July 4th

Just wanted to let you know where we are with Lemmy.world.

Issues

As you might have noticed, things still won't work as desired.. we see several issues:

Performance

Loading is mostly OK, but sometimes things take forever
We (and you) see many 502 errors, resulting in empty pages etc.
System load: The server is roughly at 60% cpu usage and around 25GB RAM usage. (That is, if we restart Lemmy every 30 minutes. Else memory will go to 100%)

Bugs

Replying to a DM doesn't seem to work. When hitting reply, you get a box with the original message which you can edit and save (which does nothing)
2FA seems to be a problem for many people. It doesn't always work as expected.

Troubleshooting

We have many people helping us, with (site) moderation, sysadmin, troubleshooting, advise etc. There currently are 25 people in our Discord, including admins of other servers. In the Sysadmin channel we are with 8 people. We do troubleshooting sessions with these, and sometimes others. One of the Lemmy devs, @[email protected] is also helping with current issues.

So, all is not yet running smoothly as we hoped, but with all this help we'll surely get there! Also thank you all for the donations, this helps giving the possibility to use the hardware and tools needed to keep Lemmy.world running!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 110 points 1 year ago* (last edited 1 year ago) (4 children)

That is, if we restart Lemmy every 30 minutes. Else memory will go to 100%

Lemmy has a memory leak? Or, should I say, a "lemmory leak"?

[–] [email protected] 43 points 1 year ago (1 children)

A pretty bad one at that...

[–] [email protected] 33 points 1 year ago (4 children)

But... but... Rust...

[–] [email protected] 55 points 1 year ago (1 children)

Rust makes holes and that's how leaks happen

[–] [email protected] 10 points 1 year ago

Underrated comment

[–] [email protected] 27 points 1 year ago

Rust protects you from segfaulting and trying to access deallocated memory, but doesn't protect you from just deciding to keep everything in memory. That's a design choice. The original developers probably didn't expect such a deluge of users.

[–] [email protected] 12 points 1 year ago* (last edited 1 year ago)

Leaking memory is safe

[–] [email protected] 9 points 1 year ago

I’m calling it - if there’s actually a memory leak in the Rust code, it’s gonna be the in memory queues because the DB’s iops can’t cope with the number of users.

[–] [email protected] 13 points 1 year ago

On some of the latest release candidates I think so.

[–] [email protected] 12 points 1 year ago

Lemmy has a memory leak? Or, should I say, a “lemmory leak”?

A lemmory meek, obviously!

[–] [email protected] 6 points 1 year ago (1 children)

Wait isn't lemmy written in rust how do you create a memory leak in rust? Unsafe mode?

[–] [email protected] 16 points 1 year ago* (last edited 1 year ago) (1 children)

let mut memory_leak = Vec::<u8>::new();
loop {
  memory_leak.push(0);
}

[–] [email protected] 9 points 1 year ago (1 children)

That's not a memory leak though. That's just hording memory. Leaked memory is inaccessible.

[–] [email protected] 2 points 1 year ago (1 children)

In the example it’s inaccessible.

[–] [email protected] 1 points 1 year ago (1 children)

It's not. The vec is still accessible and if it goes out of scope rust automatically clears the memory.

[–] [email protected] 0 points 1 year ago (2 children)

But it will never fall out of scope because of the loop

[–] [email protected] 1 points 1 year ago

Exactly but it's still accessible since it's in scope.

[–] [email protected] 1 points 1 year ago

Exactly.