MySQLTuner-perl VS testssl.sh

What helped me for one server was dedicating more of the memory to the database storage engine. In my case it was InnoDB buffer pool tweaks. If you’re running MySQL then using MySQLTuner (https://github.com/major/MySQLTuner-perl) may help but this all requires command line work so I would suggest this only being done if you’re experienced with this or getting someone experienced to help. I’ve also seen but not yet experienced that a managed database solution or a separate database server may help.

If you set the innodb_buffer_pool_size to roughly 80% of the total available memory everything gets cached and run from memory. Have you tried this? And have you tried just running mysqltuner and see what that suggests? https://github.com/major/MySQLTuner-perl

One of the biggest and best tools is MySQL Tuner and this will be good to run as it will give you specifics based on your hardware. You can also try SolarWinds. https://github.com/major/MySQLTuner-perl

Are the DBA's on this thread committing code to the MySQL [1] and Postgres [2] tuner scripts that give new DBA's all your learned advise and battle hardening experience? Or at least a repo with the same objectives?

[1] - https://github.com/major/MySQLTuner-perl

[2] - https://github.com/jfcoz/postgresqltuner

You could try to manage this query_cache_size. If you use phpmyadmin there is a tool : phpMyAdmin Advisor, it will give you advices ! Make sure your tables are innodb, not myisam. And this tool also https://github.com/major/MySQLTuner-perl I Always change one parameters at a time. And step by step to avoid unatempted effects.

You can also try out MySQL Tuner to identify some opportunities for configuration improvements. Just make sure that you thoroughly understand the settings and the effects of any changes that you might consider making since you are in a production environment.

Not a DBA, but I've had lots of success with MySQL Tuner (https://github.com/major/MySQLTuner-perl)

You’re in luck because such a tool exists :) https://testssl.sh/

Run https://testssl.sh/ and see what ciphers are being offered.

There is https://github.com/drwetter/testssl.sh utility. It can help diagnose issues (e.g. diffs between working and non-working sites).

For internal use, there's https://testssl.sh/

The current configuration allows for TLSv1 to TLSv1.3 connections. I can verify those using testssl.sh, the tests will succeed (although correctly mentioning, that TLSv1 and TLSv1.1 should be disabled). Running the tests again after about 5 minutes, the results are different. TLSv1.2 now shows "not offered and downgraded to a weaker protocol".

testssl.sh