-------- Recommendations ---------------------------------------------------------------------------
General recommendations:
    Run OPTIMIZE TABLE to defragment tables for better performance
      OPTIMIZE TABLE `probankrot`.`cache`; -- can free 438.10181427002 MB
      OPTIMIZE TABLE `probankrot`.`cache_form`; -- can free 4437.50187683105 MB
      OPTIMIZE TABLE `probankrot`.`cache_views_data`; -- can free 128.98123550415 MB
      OPTIMIZE TABLE `probankrot`.`watchdog`; -- can free 5868.7052116394 MB
      OPTIMIZE TABLE `torgigov`.`cache_form`; -- can free 196 MB
    Total freed space after theses OPTIMIZE TABLE : 11069.2901382446 Mb
    Set up a Secure Password for user@host ( SET PASSWORD FOR 'user'@'SpecificDNSorIp' = PASSWORD('secure_password'); )
    Enable the slow query log to troubleshoot bad queries
    Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1
    Increasing the query_cache size over 128M may reduce performance
    Increase table_open_cache gradually to avoid file descriptor limits
    Read this before increasing table_open_cache over 64: http://bit.ly/1mi7c4C
    This is MyISAM only table_cache scalability problem, InnoDB not affected.
    See more details here: https://bugs.mysql.com/bug.php?id=49177
    This bug already fixed in MySQL 5.7.9 and newer MySQL versions.
    Beware that open_files_limit (2158) variable
    should be greater than table_open_cache (1024)
    Consider installing Sys schema from https://github.com/mysql/mysql-sys
    Before changing innodb_log_file_size and/or innodb_log_files_in_group read this: http://bit.ly/2wgkDvS
Variables to adjust:
    query_cache_size (=0)
    query_cache_type (=0)
    query_cache_size (> 983M) [see warning above]
    table_open_cache (> 1024)
    innodb_buffer_pool_size (>= 57.2G) if possible.
    innodb_log_file_size should be (=61M) if possible, so InnoDB total log files size equals to 25% of buffer pool size.
    innodb_log_buffer_size (>= 8M)