All done ๐ค
Lemmy.ca's Main Community
Welcome to lemmy.ca's c/main!
Since everyone on lemmy.ca gets subscribed here, this is the place to chat about the goings on at lemmy.ca, support-type items, suggestions, etc.
Announcements can be found at https://lemmy.ca/c/meta
For support related to this instance, use https://lemmy.ca/c/lemmy_ca_support
wow awesome. that was quick!
Even our Lemmy instance takes Canada as a stat holiday
wait the maintenance already finished?
Yep!
The Scotty Principle (also known as The Scotty Effect or The Scotty Factor) is the technique of adding extra time to your estimates when asked how long a task will take so that you appear to be a wizard when you accomplish the task quicker than you first claimed.
Also gives you some buffer time if things go sideways.
Thanks for your hard work!
Good luck, and happy Canada day!
Happy Canada day. And wow! The instance is extremely fast now. Thank you!
We won't accept anything less than extremely fast!
It's a big difference going from a 8vCPU 8GB RAM VPS where the actual resources were likely quite over subscribed to a dedicated server with a 6c/12t Ruby Lake Xeon, 32GB RAM, 2x 512GB NVMe drives in RAID with it's own 1Gbps Public connection. From the data we have it should be sustainable with this server until about 40-50K users.
We're currently paying ~$140/month for that, and have plans in place to scale up as needed when it's needed. Over the next few days we will reopen the ability to make donations to cover the costs of operations.
@[email protected] > Over the next few days we will reopen the ability to make donations to cover the costs of operations.
I'll be present :)
Was it CPU or memory bound prior to the upgrade? Or IO?
All of the above, but more so memory and IO.
Disk or network IO?
Disk, due to low memory. Not enough to keep enough of the db in memory, and having to hit disk for pictures as well.
Oh I see. Makes sense. Do you know if the storage was NVMe previously or spinning media?
It was a VPS and I think on some sort of shared SATA/SAS SSD array, just going off the 300-800MB/s reads I was seeing.
Old box: Timing buffered disk reads: 2066 MB in 3.00 seconds = 687.62 MB/sec
New box: Timing buffered disk reads: 1022 MB in 0.31 seconds = 3338.77 MB/sec
Nice uplift. Random IO which is likely what the db does are probably through the roof compared to the sequential uplift.
The DB is small enough it's all in ram now, seeing a 100% cache hit rate in postgres.
Nice. You could post any screenshots and copy-pasta if you collect them anyways from stuff you find interesting while working on the instance. I'm sure there's a lot of technical folks around here other than us that would find it fun to look at. Only if it's not significant additional work of course. ๐
Happy Canada Day!
Are there plans to bump to v0.18.1 at the same time? Only asking as my themes will need to be updated when we do.
0.18.1 hasn't been officially released yet, it's still an RC. We're probably going to hold until it's official. New server will still be 0.18.0.
As much as I'm looking forward to the improvements in the latest Release Candidate, this is definitely the right call.
Best of luck with the server migration and happy Canada Day!
Yeah same here, looking forward to the fixes but making sure it gets tested properly first =)
Do you have an updated copy of your theme already? If you send it ahead of time, happy to drop it in whenever we do the upgrade.
This should get us going: https://pastebin.com/TxTNn8y5
I'm reworking the theme a bit and trying to shape it into something that stands on its own.
Applied!
Thanks! Unfortunately, I've had to push more updates, because many frontend elements have changed even between the v0.18.1 release candidates. This may be an impossible task to maintain as a native theme option.
For now, the layout changes appear to be working as intended but most of the colour changes are not. I'm wondering if we should just pull the plug on this approach before too many users grow dependent.
I'm maintaining a version for Stylus and other CSS injector add-ons on Github. It's also available at UserStyles, and these might be the most sensible solutions as I can update them on the fly.