3 ms·
> 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
by 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.