@gdgsupport or some other member here has ideas / tips to reduce the mySQL folder size?
The mySQL folder is around 123mb pretty large addition to final app size. My table size is less than 150kb…
Seems I recall asking something about this is past but pretty sure it was on V2 Beta thread and now gone.
Thanks in advance.
One of the things that works in standard mySQL install on a server is reducing log file size, but can’t seem to get working with EXEOut.
For instance on a small server I would rm the log files and:
restart mysqld, InnoDB notices that the files are missing, and creates new file at the new size according to the innodb_log_file_size variable in cfg
Changing the innodb_log_file_size to something smaller (like 5mb each) in my-innodb-heavy-4G.ini has no effect.
Notice in logs:
2017-10-29 13:55:00 5456 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-10-29 13:55:00 5456 [Note] InnoDB: Completed initialization of buffer pool
2017-10-29 13:55:00 5456 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB
2017-10-29 13:55:02 5456 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB
Where is the cfg that sets sizes to 48 MB?
Normally it’s the my.cfg file.
Check this too:
In order to change innodb_log_file_size safely, you need to shut the server down cleanly and move away (don’t delete) the log files, which are named ib_logfile0, ib_logfile1, and so on.
Anyway, if you package your folder with Paquet Builder for distribution, all files will be highly compressed.
Yea, finally found but changing to anything below 48MB causes strange behavior. End up with error logs. Never had the issue in all my years but guess there is something internal that EXEOut does not like about reducing size.
Even sites on some pretty large VPS boxes does not need a 48MB size. Strange that EXEOut needs that much.
Check this too:
Yes of course this is the correct way and the way I do for real servers. Tried this with EXEOut and will not work. Becomes unstable and produces error logs.
Not saying I am a server guru, but been building / configuring servers for many years. Worked in job that required this experience.
Anyway, will continue to look for a solution. Maybe if you guys decided to allow securing (encrypting) sqlite will no longer have need mysql;)
We’ll also experiment on our side with the MadiaDB server to reduce size of logs.
Did you upgrade to the last v2.2.1? It fixes the bug you mentioned about File Properties.
I have not yet upgraded. Just getting back into my office today from week long seminar trip. Will give it a try later today.