Update The upgrade was done, DB migrations took around 5 minutes. We’ll keep an eye out for (new) issues but for now it seems to be OK.
Original message We will upgrade lemmy.world to 0.18.3 today at 20:00 UTC+2 (Check what this isn in your timezone). Expect the site to be down for a few minutes. ““Edit”” I was warned it could be more than a few minutes. The database update might even take 30 minutes or longer.
Release notes for 0.18.3 can be found here: https://github.com/LemmyNet/lemmy/blob/main/RELEASES.md
(This is unrelated to the downtimes we experienced lately, those are caused by attacks that we’re still looking into mitigating. Sorry for those)
Sorry for those
It’s not your fault :) We know you admins are working really hard to keep the server as stable as possible.
Don’t humanize them, they’ll expect us to always treat them with respect! /s (obvs 🙄)
- Add controversial ranking
- Change logic for determining comment default language
- Add infinite scroll user option
Neat. I hope the comment language logic change means the default won’t be “Undetermined” anymore.
I’m sure the attacks are just as annoying for you guys as they are to us, if not more. Appreciate the update.
Edit: Loving the endless scroll for the front page! I’ve been eagerly awaiting that. Such a small change, but such a big impact.
Release notes for 0.18.3 can be found here: https://github.com/LemmyNet/lemmy/blob/main/RELEASES.md
Thanks, added to the post
Thanks, will put this in the post
Fwiw, it can be helpful to call out the date for such changes. Preferably in YYYY-MM-DD (ISO 8601).
While it’s helpful to link to an off-site timezone converter tool (thanks for that, btw), “today” can be a different date, depending on where in the world you are. For example, Japan, Australia, and New Zealand.
Good point
Even better is “when this post is N hours old” :)
As someone who has had to grind through heaps of logs over the years, from systems in various timezones, from products that disagreed on the ‘best’ datetime format, I’ve become a fan of adopting ISO 8601 as much as possible. For personal systems such as a laptop, that’s a different story. But if I’m spinning up an EC2 instance in
us-west-2
or a VM in Central Europe, I avoid the whole “err, what TZ is this in, or should even be in?” decision-making process and just run with WHO CARES IT’S SET TO UTC NOW LET’S MOVE ON ALREADY 😀And not that anyone here is likely to care, but here’s a quick shout out to lnav - The Logfile Navigator for grinding on system logs (for systems where something like Prometheus or whatever hasn’t been proactively set up).
ISO8601 is the only way to go.
Great! Thanks for keeping things up to date and running!
Minor suggestion: write your time zones like UTC+2 and not CEST. I’m pretty sure most people outside Europe don’t know what the time zone CEST is. Yes, you provided a link that helpfully converts the time to the users’ local time zone, but sometimes it’s nicer to be able to know something without having to click into a link.
OK, updating the post
Wow, you actually changed it! I was kind of shocked when I came back to my feed seeing UTC+2 in the title. Thanks! :D
Yep, I like good tips like these. :-) Thanks
Super nitpick. Can we just use 1800 utc? Then everyone can convert to their zone directly. *signed me in a CEST zone.
yeh, the actual utc time is much more straightforward than +2
I keep one of my spare clocks set to UTC for exactly this.
it would be nice if Lemmy had support for formatting Unix timestamps in whatever timezone whoever is looking at it is in, like discord
That could be fixed in the apps and UI:s as a cosmetical improvement based on a timezone entered in the user settings. UTC is… universal.
The problem with open-source for me is reading ideas like this and having to deal with the frustration of not knowing how to write it myself.
Here is an alternative Piped link(s): https://piped.video/watch?v=-5wpm-gesOY
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.
Really liking the transparency with the community over how the server is doing.
Great work.
This version brings major optimizations to the database queries, which significantly reduces CPU usage. There is also a change to the way federation activities are stored, which reduces database size by around 80%.
Is it me or is the 80% figure just insane? Are there any benchmarks to see how fast this has become versus say Lemmy 0.18.2 on a very large instance?
Is it me or is the 80% figure just insane?
Not really, you’d be surprised how often systems are bloated all because of a single option, character, etc. Most developers don’t start optimizing until much later in the software’s lifecycle. Often enough, it is easily overlooked. That’s why code reviews are needed often with fresh pair of eyes.
Just to set the expectations, reducing database size or CPU usage does not necessarily mean it is faster but it does mean there’s more free capacity on the servers to handle more users at the same performance.
More importantly; they may help reduce costs on the smaller indie instances that doesn’t need to buy larger server instances.
Hopefully, we’ll continue to see more of these optimizations.
I believe if the backend doesn’t have to write as much data then you’ll have less I/O operations so it should IMO have an impact on the overall speed of Lemmy (unless all of those operations are done asynchronously). Same for the reduced CPU usage, it could allow for more stuff in parallel.
Speed/pref and capacity are two separate things. I/O has nothing to do with the size of the database. You can write 100TB per second into the database and choose to only store 1TB of content. That does not mean the app is writing 1TB per second, it is still writing 100TBps.
They said they changed how the activities data is stored, which reduced the size by 80%; here’s one of the changes they made: https://github.com/LemmyNet/lemmy/issues/3103
As you can see, the issue here is that they were storing a lot of data in the activities table that is not needed, it was only meant for debug purposes. So, they split up the data into two and not store the other data as it isn’t needed; they’re still writing these data the same as before. One part is used to ensure they don’t re-process the same data but this is the same thing they were doing before this change.
In addition, they’ve limited how long the data is retained for 3 months, which is a separate job they run to remove data.
All of this has zero impact on the users using the app right now. The main benefit is for instance admins with limited storage. One might say the system slows down if there’s not enough space but that is still the same case here with this MR, it will still slow down.
Funnily enough, this is the feature that can speed up the performance by doing less calls:
The federation code now includes a check for dead instances which is used when sending activities. This helps to reduce the amount of outgoing POST requests, and also reduce server load.
Thank you for the heads up!!
2pm EST for us silly Freedum Unit folks.
EDT actually, not EST.
oh yeah, forgot about that. Could’ve just put ET.
Phone Home
Lol. Word is the update gives a boost to smaller communities. Looking forward to this!
2PM Entertainment Tonight
Looks like the upgrade is done and was a quick and easy success, thank you Devs!
Why are these announcements the only place I am finding out the Lemmy has an update? I figured there would be more top level discussions about it on Lemmy. Maybe I am just not following the correct communities.
There is an official announcement here: https://lemmy.ml/post/2540874
If announcements of Lemmy releases are what you’re after, !announcements@lemmy.ml is a place for you. But in broader picture, subsequent updates are usually just not that big of a deal.
Each server admin decides how to publish announcements, some have a mastodon account, some have a separate website, some might post on a different Lemmy server, like !Fediverse@lemmy.ml, someone would likely post up there after the fact if the server is down for a while without apparent explanation.
Smooth! Curious about the new DB size
Down from 12GB to 1.8GB…
Wow, thats awesome for the backups and scalability!!
Me too. Creating a db dump now…
How do you turn on endless scrolling? I’m still seeing page numbers
Number 1 thing I miss from reddit w/ RES. 😫
Infinite scroll and work filtering. If I see one more post about “AI”, Musk, Twitter, or fake superconductors, I might have to get off the computer for 10 whole minutes.
Post hiding would be great to have.
Strange it worked out of the box for me.
Will it change the behaviour of sorting by hot? seeing post from years ago is funny
Yes, the 0.18.3 changelog has
Fixing hot_ranks and scores to append a published sort
as one of the items.