352 MB is not really “high memory usage”, considering all the services Virtualmin uses. Apache, Postfix, BIND, MySQL, ClamAV and SpamAssassin (if activated)… All of that together does use quite some memory.
If you absolutely need to reduce that, you should first turn off all features in Virtualmin you don’t need, and then deactivate (not uninstall! can lead to dependency issues) the corresponding Linux services using Webmin “Bootup and Shutdown” module. You can also instruct VM in the initial setup wizard to not pre-load libraries and not use the “domain-lookup” service. All of that of course means your system performance will be considerably degraded.
Each individual service can possibly be configured concerning memory usage too. MySQL has options for that, as does Apache. I’m not aware of BIND options for that though.
But again, if 350 MB memory usage for a full hosting system is too much in your opinion, you might want to re-think that opinion.
350 of 1025 MB might be a “high percentage”, if you will, but as I said, in absolute figures, 350 MB is not too much for all the services Virtualmin starts by default.
And I gave you some hints how to reduce the memory requirements. I believe there are also some instructions here on the forum or in the documentation section about running Virtualmin in a low-memory environment.
You can apply the same MySQL configuration changes in Virtualmin that you used for this Kloxo thingy. Vmin does not support djbdns/tinydns though.
Then again, if your system uses 33% of its available memory with all required hosting services started up, that’s fine, isn’t it? What’s the problem exactly? What were you planning to use the unused 66% for?
