this post was submitted on 01 Jul 2023
127 points (97.7% liked)
Lemmy.ca's Main Community
3465 readers
4 users here now
Welcome to the lemmy.ca/c/main community!
All new users on lemmy.ca are automatically subscribed to this community, so this is the place to read announcements, make suggestions, and chat about the goings-on of lemmy.ca.
For support requests specific to lemmy.ca, you can use [email protected].
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
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. 😁