You should refactor as needed as you go because refactoring cases are never gonna be prioritised.
That sounds like bug propaganda right there
There's a markdown entry thing in the drop down menu that'll convert your MD to their formatting.
By doing this the connections are all severed, the RAM is freed up, and it’s all good again.
Ah, neat! I didn't think of that. You can limit the size of the connection pool in your lemmy config fwiw.
Nice, that looks like it's doing a similar thing to my weird mess of SQL and Python that I did last year haha
Good luck for the migration :)
cronjob to restart the backend lemmy container
Fair enough, that'd work. I run my database in a different pod to lemmy (I run this all in kubernetes), and I cannot restart that pod without causing an outage for a bunch of other things like my personal website. I ended up just needing to tune my config to have a maximum RAM usage and then configuring k8s to request that much RAM for the DB pod, so it always has the resources it needs.
pictrs image cache is 250-300gb
oof :(
That's what my custom lemmy patch was, it turned off pictrs caching. That's now in lemmy as a config flag (currently a boolean but in 0.20 it will be on/off/proxy where the proxy option goes via your pictrs but does not cache). I then went back through mine and did a bunch of SQL to figure out which pictrs images I could safely delete and got my cache down to 3GB.
Interesting. I have some New Relic stuff setup with my cluster but most of that is just resource usage stuff. I ran out of RAM a while back so I've had to be a bit more restrictive about how many connections Lemmy can have to postgres db.
There’s no progress meter and so far it has taken 2 days 😱.
Uh oh. I considered updating to 0.5 as part of my 0.18.3-ish (I was running a custom fork I made with some image caching stuff that has since been merged in to real lemmy) -> 0.19.3 upgrade but I'm glad I didn't.
Thanks for the heads up. Are you migrating to postgres for pictrs too, or sticking with sled?
These are pretty neat graphs! Is it sourced from the Prometheus logs?
Just updated to 0.19.3 but the DB migrations failed due to a permissions change I made a while back to my DB, so I had to spend a few hours in the SQL dungeons fixing things.
Yeah, I'm not justifying the annexation.
Technically only some of HK was under the lease, some was indefinitely controlled by the British. However, you're still right because of the military force difference.
The Breville Bambino (Plus) with a nice grinder is basically an impossible value-to-money ratio to beat. Also remember to factor in a scale that's accurate to 0.1g, a cheap WDT tool with thin needles (i.e. 0.35mm), and a dosing funnel to make the WDT not messy. If your budget is limited then you can skip the WDT tool I guess.
I wouldn't go for the Barista Express/Pro because the built in grinder is not very good. The "impress" version of the Barista Express could still be worth it if you're not looking to make espresso a hobby and just want something easy that will make tasty drinks. I'd recommend joining the Espresso Afficianado's discord server, which is where a lot of the /r/espresso long-stays moved to after the reddit API stuff. There's a channel for beginners that can help you get started.
I attempted to boot Mandrake/Mandrivia on an old laptop once and failed, then I mucked around in Slackware's live CD for an afternoon. The first thing I actually installed and used daily was Ubuntu 10.04.
In my experience I haven't had an issue because usually the refactorings are small. If they're not I just hop on a call with the person who wrote the MR and ask them to walk me through it.
In theory I'd like to have time to dedicate solely to code health, but that's not quite the situation in basically any team I've been in.