Very high latency, though. Great for some use cases, useless for others.

It wasn’t named by IT people, though. It was named by academics. And it’s not about using computers, it’s about computing. Computer science is older than digital electronics.

Besides RAM, what resources do for think you’re saving? Not CPU cycles or IO ops, because you’re processing the same amount of DB queries either way. Not power consumption, since that isn’t affected by RAM utilization. Maybe disc space? But that’s even cheaper than RAM.

Or more importantly: the extent to which you can self-host out of sheer luck and ignorance like you suggest is very limited. If you don’t want to engage with a minimum amount of configuration, you might bump into security issues (a much broader and complex subject) long before any of the above has a material impact.

You’re mischaracterizing what I said. My point is that running multiple DB processes on a server isn’t going to have a significant impact on system load, if all other factor are kept constant.

You seem to be obsessed with optimising one resource at the expense of others. Time is a limited resource, and even if it only takes 5 minutes to configure all of your containers to share a single db backend (it will take longer than that even if you just have 2), you’re only going to save a few MB of RAM. And since RAM costs roughly $2.5/GB (0.25 cents/MB) your time would have to be worth very little for this to be worthwhile.

On the other hand, if you’re doing it to learn more about computers then it might be worthwhile. This is a community of hobbiests, after all…

Neither, I’m trying to explain that you don’t need to know the implementation details of the software running on your server to backup the entire thing.

Where are you getting that from? The fastest and easiest way to back up any server is a full filesystem backup, especially if you’re using something like zfs or btrfs.

I’m saying this based on real world experience: after a certain point you start to see deminishing returns when optimizing a system, and you’re better off focusing your efforts elsewhere. For most applications, customizing containerized services to share databases is far past that point.

What’s the point of posting if your comment isn’t going to be visible?

Do you have the data to back that up? Have you measured how much of an impact on system load and power consumption having 2 separate DB processes has?

Roughly the same amount of work is being done by the CPU if you split your DBs between 2 servers or just use one. There might be a slight increase in memory usage, but that would only matter in a few niche applications and wouldn’t affect environmental impact.

This argument is usually followed by the racist dog whistle “it’s unfortunately our demographic”

I’ve mostly seen it followed up by criticism about American culture and lack of access to healthcare, specifically mental health.

For most applications the overhead of running a second DB server is negligible.

I write software for a living, and have worked with all 3 database options in the past. I don’t know what DB backend my nextcloud server is using, nor do I care.

Also covered by countless bands from every genre.

(not a complaint)

Everything on ollama can be run locally without much work. Assuming you have the GPU to support it…

https://ollama.com/

Heh, seems like you hit a nerve with that poster.

To answer your question - IMO it’s still that bad, but I’m not sure what the right way to respond is, either.

Not me, I’d rather work on a clean code base without any slop, even if it pays a little less. QoL > TC

No, check ebay if you don’t believe me. It’s not exactly plentiful, but there are enough contractors with several hundred/thousand feet left over from big jobs who are selling it for wholesale or less. It’s not like you can recycle it, and splicing is unreliable without tools that cost as much as a car, so if you’ve got a partial spool you need to get rid of you’ll probably have to sell it at a loss.

Roll tide.

The high school I went to let seniors who had jobs leave at noon. They took the core classes but not electives and were allowed to graduate as long as their boss confirmed that they were working and not just skipping class. It was legal.

Yes, but even living across the street from a hospital doesn’t guarantee you will have access to medical care. Plenty of people who live in the city can’t afford an ambulance or hospital stay.