Anton Aleksandrov

I will close this ticket, I have answered in other thread:)

I will close this thread now. If you still have questions, feel free to contact me.

During benchmark scripts will run massive, enormous amount of SQL queries – especially what relates to inserting data. During normal WP operation – you’ll never see it (unless you run some import). But that’s the only way to benchmark database server. Those setting disable few things, fine tune a bit for better performance.. well, if I have to be super honest – better performance with slightly more resource usage and sliiightly degraded redundancy (which with modern hardware hardly ever happen) – everything in this world has its price..

I have some suggestions on my page : https://wpbenchmark.io/improve-wordpress-speed/

what database server version are you using? MySQL or MariaDB? If you try to add those configuration options to your my.cnf – i think there should be some improvement. ??

Hm, could you explain it better? Sounds strange, that Redis did not let you remove the plugin or give any problems..

I think those will also work in MariaDB, but they won’t be so critical there, mostly due to better default values in MariaDB. ??

Strange.. What error is it giving in Immunify360?

The following settings can slow things. They have their meaning, but speed will be the price for it.

innodb_flush_log_at_trx_commit = 1

I would increase these, but personally have not seen huge impact

innodb_read_io_threads = 4
innodb_write_io_threads = 4
thread_cache_size = 64

If you have enough memory, increase this:
innodb_buffer_pool_size = 512M

A bit unsure about MySQL 5.7, but I have just discovered, that the following settings help a lot for MySQL 5.8.30+

# especially for MySQL 8.0
innodb_redo_log_capacity=512M # only if you have MySQL 8.0.30+
innodb_log_buffer_size=512M
innodb_log_write_ahead_size=128K
disable_log_bin

Can you try adding them to your my.cnf? Especially the “disable_log_bin”. The first parameter might not work for you.

Technically mpm-event is also multithreaded. But apache does not run your PHP scripts, unless you use mod_php. And even with mod_php – I believe that one script is still being processed with one core.. So it matters to have fast cores.

Here is a solution (posting here, so others can benefit from it).

If you are running MySQL8 on slow disks (e.g. SATA) and benchmarks are failing, most likely you need to add these configuration options to your MySQL config (/etc/my.cnf)

# default 100M
innodb_redo_log_capacity=512M
# default 16M
innodb_log_buffer_size=512M
# default 8kb
innodb_log_write_ahead_size=128K
# binlog is enabled by default
disable_log_bin

The biggest impact you will feel after adding “disable_log_bin”. Other options help a lot.

Important: the “innodb_redo_log_capacity” setting is only available from MySQL 8.0.30

As always for performance – suggest setting :
innodb_flush_log_at_trx_commit = 2

• This reply was modified 1 year, 11 months ago by Anton Aleksandrov.

Can you please run test and send me URL of the results? Feel free to contact me by email info at wpbenchmark dot io. ??

Sorry guys, missed this support forum.
I have fixed it in the latest version, just released.

Sorry guys, missed this support forum.
I have fixed it in the latest version, just released.

Is it possible to get a trial account there to test myself and see any possible errors in the logs?