| SYSTEM INFORMATION | |
|---|---|
| OS type and version | rcoky 10 |
| Webmin version | 2.520 |
| Virtualmin version | 7.50.0 |
| Webserver version | Apache version 2.4.63 |
| Related packages | SUGGESTED |
hello,
when install new fresh virtualmin .
at first config ask default memory of mariadb/mysql
i don’t remember what i clicked.
so wehre is this option?
i search in servers - mariadb (variables - config files)…
or in system settings - virtualmin configuration
i find anything… 
can you help me?
thank you
Well, you can Re-Run Install Wizard under Virtualmin → System Settings.
But I wouldn’t bother. Mariadb optimizes its settings as per the system config regardless of what we choose here, I feel.
thank you for reply.
i try but i can change only password not default memory used by mysql/mariadb
thank you
We’ve removed that from the wizard, AFAIK. It was just a UI for selecting among the example configs shipped with MySQL/Mariadb, and the upstream stopped shipping those example configs and stopped suggesting people use them for “tuning”.
In general, most people should just leave it alone, unless they’re going to invest the time to analyze their specific hardware and usage patterns to tune it appropriately.
The old configs were tweaking some knobs that probably shouldn’t be tweaked anymore. Again, if you have database performance problems, you should tune for your workload and your hardware. Tools like MySQL-tuner may be helpful (it supports Mariadb, too). GitHub - major/MySQLTuner-perl: MySQLTuner is a script written in Perl that will assist you with your MySQL configuration and make recommendations for increased performance and stability.
In short: That page in the wizard is gone and you don’t want it.
ok thank you for reply!!! 
i have a problem OOM with mariadb
server have only 1 domain (wordpress)
have 8gb and seems strange …
but then i realize that error is in fpm
i had setup
PHP service maximum sub-processes = 64
now i setup (as default)
PHP service maximum sub-processes = 16
now mariadb is up from 3 hours…
big thank you
The OOM killer doesn’t necessarily kill the process that caused the memory exhaustion. In fact, it rarely does. It usually kills something mostly innocent, because the kernel tries to figure out what will be least disruptive, which means something that’s not very active, relatively speaking, but also large enough to free up enough memory to satisfy the recent allocations.
ok thank you.
now if happens again i search in this direction
thank you again
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.