Skip to content
This repository has been archived by the owner on Jan 27, 2024. It is now read-only.

MySQL Optimization and InnoDB engine #80

Closed
shawniverson opened this issue May 1, 2014 · 3 comments
Closed

MySQL Optimization and InnoDB engine #80

shawniverson opened this issue May 1, 2014 · 3 comments

Comments

@shawniverson
Copy link
Member

http://forum.efa-project.org/viewtopic.php?f=13&t=617

@shawniverson shawniverson added this to the 3.0.0.6 milestone May 3, 2014
@banym
Copy link

banym commented Jul 26, 2014

Oh sorry, didn't want to have this commit linked back here since it is not complete, yet. It was more meant as a reminder for me to know where I was working at.
Still needs some testing and modifications, will make a pull request when it's done.

What do you think about setting the InnoDB configurations for a 2GB system, or should there be a automatic detection for the amount of available memory or a manuall configuration option in the EFA configuration tool?

Regards,

Dominik

@darky83
Copy link
Contributor

darky83 commented Jul 27, 2014

E.F.A. minimum memory is configured at 2GB.
But this is for all items (mailscanner, postfix, webserver mysql etc...)
So effectively mysql should probably be configured to run with max 1 GB for a default setup and manual adjustment in EFA-Configure if users add more memory.

@shawniverson shawniverson modified the milestones: 3.0.0.6, 3.1.0.0 Sep 26, 2014
@shawniverson
Copy link
Member Author

InnoDB upcoming default in MailWatch.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants