this post was submitted on 01 Jul 2023
68 points (97.2% liked)
Lemmy.ca's Main Community
2825 readers
3 users here now
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
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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. 😁