3 ms·
> Doesn't work that way with containers - they can all still have access to all the memory It's not a container problem I'm summing up here, it's a DB problem.
by falcolas 10y ago
> Doesn't work that way with containers - they can all still have access to all the memory
It's not a container problem I'm summing up here, it's a DB problem. Well behaved DB software won't grow to boundless limits to manage the workload, it will grow to it's configured limits.
Running multiple instances of a DB server means that each DB is going to be hard-coded to a limit which is some fraction of the available memory.
> I have yet to deal with a server where adding more RAM was more than a rounding error
There are limits even to this, though. The most memory you can get for any single, broadly available instance in AWS is 244 GiB, and its going to cost you an arm and a leg to run. It's not hard to create a dataset which exceeds 244 GiB in size.
> take down all of them to upgrade any one of them
Only if you're upgrading the actual DB software. And most time a master switch is sufficient to keep everything online through a DB version upgrade. Not to say that master switches are easy; but even Uber has that pain with their system.
> all of them being able to run on the same database version, and with the same extensions.
This isn't something I frequently see being an actual problem, within the same corporation.
- vidarh 10y ago> Running multiple instances of a DB server means that each DB is going to be hard-coded to a limit which is some fraction of the available memory. What you are suggesting then, is setting limits in a way that does not guarantee resources for any given database. > There are limits even to this, though. The most memory you can get for any single, broadly available instance in AWS is 244 GiB, and its going to cost you an arm and a leg to run. It's not hard to create a dataset which exceeds 244 GiB in size. Most people don't have databases that large. If you do, perhaps you shouldn't be puting multiple of them in a single instance if you're limited to machines that small. For comparison, I have servers with dozens of databases that fit into memory on machines with 64GB and less. I also have machines with single databases that need far more. If we need to, we'll provision machines with 1TB-2TB of RAM. > This isn't something I frequently see being an actual problem, within the same corporation. It's something I see all the time. Consider that "within the same corporation", people often run databases for a large number of external customers, or need to be able to roll out new versions, or do development and testing on different versions. I have at least 5 different versions of Postgress sitting on production servers right now due to customers with different requirements and different upgrade cycles. I also have several different versions of MySQL.
- falcolas 10y ago> does not guarantee resources for any given database Correct. Instead it gives the most resources to the pages in all of the databases which are accessed and used the most. MySQL and InnoDB are remarkably well tuned to ensure that the most often used pages are in memory, where they can be accessed and updated with the greatest performance. > It's something I see all the time. We apparently work on very different usecases. Fair enough. Just be aware that your usecase is far from typical. Continuing to argue points across such diverse usecases isn't going to make for a productive discussion.
- vidarh 10y ago> Instead it gives the most resources to the pages in all of the databases which are accessed and used the most. And that's not acceptable when dealing with setups where each database needs predictable performance, and some of them may see heavy traffic while others don't. > Just be aware that your usecase is far from typical. I don't think there is such a thing as a "typical" usecase in this area based on what I see as part of my consulting work, but this is common enough that I deal with it regularly across a wide variety of clients.