MySQL Tweaks

woodlandcapital

Hey,

After getting all of the Premium modules installed there were some issues retrieving the objects and recordsets through MySQL workbench over and over. I put together a list of changes for your mysql configuration to process the InnoDB engine a little better. I went from ~10minute download of records to about 25 second download of records. Hopefully this will help some other users. I located my mysql config in /etc/my.cnf on CentOS:

[mysqld]
innodb_flush_log_at_trx_commit=1
innodb_buffer_pool_size=128M
innodb_thread_concurrency=1
innodb_flush_method=O_DIRECT
sync_binlog=1
expire_logs_days=2
innodb_file_per_table=1
innodb_file_format=barracuda
innodb_strict_mode=0
innodb_fast_shutdown=0
ignore-builtin-innodb
plugin-load=innodb=ha_innodb_plugin.so

eliminator

[quote:2gc5khts] I went from ~10minute download of records to about 25 second download of records[/quote:2gc5khts]

May I know how many records do you have?

jasiek

What do you mean by "download of records" ?

EPESI loading time when opening the application can be long - depending on your network connection speed, server configuration etc. - but still within few seconds. For example our EPESI loads in about 2.5 - 3 sec.
After the application loads any subsequent pages should be much quicker and our goal is to be less than 1 sec. For example opening CRM Companies group takes about 900 ms (0.880 sec to be exact):

Module loading time

If you are getting 25 sec than you have a serious configuration problem (not to mention ~10 min reported earlier). The only time to get such a high loading time would be running some report that collects and calculates a large number of records or importing data. Otherwise it should be rather quick. Is the performance of your installation of EPESI similar to what you get on our demo? http://epe.si/live-demo

jasiek

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

woodlandcapital

Didn't expect to have so many replies. I apologize for not responding sooner. I used some ambiguous terminology in the OP. I meant through MySQL Workbench downloading of objects and tables. It took close to 10 minutes with the original setup. This could have been due to a number of issues, especially my MySQL configuration. I frequently reach my container cap on memory with 8 users logged in and performing maintenance on phpMyAdmin. If you experience services dropping out in conjunction with running an EPESI instance, you should note your memory usage.

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge