{"id":70,"date":"2017-06-26T00:00:00","date_gmt":"2017-06-26T00:00:00","guid":{"rendered":"http:\/\/ssdnodes.billabailey.com\/2017\/06\/26\/tutorial-speeding-up-mysql-without-using-the-cpu\/"},"modified":"2025-05-18T13:37:15","modified_gmt":"2025-05-18T13:37:15","slug":"speeding-up-mysql","status":"publish","type":"post","link":"https:\/\/www.ssdnodes.com\/blog\/speeding-up-mysql\/","title":{"rendered":"Tutorial: Speeding Up MySQL Without Using the CPU"},"content":{"rendered":"

We recently had a user ask us a relatively simple question: How do I speed up my MySQL query performance without just relying on the CPU?<\/p>\n

For those who run websites or applications that rely on MySQL databases, this is an incredibly important question, as it can mean the difference between a smooth experience and one that causes frustration for both you and your users.<\/p>\n

In this tutorial, we\u2019ll cover three methods of either improving the MySQL database performance, or establishing methods of reducing the need to query the database in the first place.<\/p>\n

<\/a>Prerequisites<\/h2>\n
    \n
  1. A VPS (any OS works) running a MySQL database<\/li>\n<\/ol>\n

    <\/a>Option 1. Percona Wizard<\/h2>\n

    Percona<\/a> offers a free-to-use configuration wizard<\/a> for MySQL, which makes it easy to establish a baseline configuration that\u2019s better suited for exactly the kind of problems you\u2019re going to throw at your database. With a solid foundation to work from, you can get your service going quickly and then aim to improve performance later with further tweaks.<\/p>\n

    Note: Percona recommends this configuration wizard only be used for new servers\/databases, not ones that have been running and contain data. The primary reason is that if you replace your old configuration with one created by this wizard, your database might become inaccessible. If you already have an active database, it\u2019s probably best to skip to the second option.<\/em><\/p>\n

    If you\u2019re an SSD Nodes customer, here\u2019s a few answers related to our platform that will help get you started:<\/p>\n

    Where is this server hosted?<\/strong> Other<\/p>\n

    Do you use virtualization?<\/strong> Other<\/p>\n

    What type of storage do you use?<\/strong> SSD\/Flash<\/p>\n

    How many CPUs does your system have?<\/strong> 4 (unless you\u2019re on our smallest plans)<\/p>\n

    What is your operating system?<\/strong> Linux<\/p>\n

    The rest are entirely dependent on your particular application, although selecting the defaults in most cases will establish you with a good starting configuration that you can build from in the future. After moving through the seven steps of the wizard, you\u2019ll get a configuration that you can drop into your my.cnf<\/code> or my.ini<\/code> files on the server in question.<\/p>\n

    <\/a>Option 2. mysqltuner.pl<\/a><\/h2>\n

    This popular script scans your MySQL database and offers up warnings about vulnerabilities or weak passwords, and also gives logical suggestions as to which configuration tweaks will improve performance.<\/p>\n

    To download the script, you have two options: clone the entire repository, or take only what you need in a more \u201cminimal\u201d installation.<\/p>\n

    Clone:<\/strong><\/p>\n

    $<\/span> git clone<\/span> https:\/\/github.com\/major\/MySQLTuner-perl.git<\/span>\n$<\/span> cd<\/span> MySQLTuner-perl<\/span>\n<\/code><\/pre>\n
    After this, you\u2019re ready to start the script. More on that in a moment.<\/p>\n
    Minimal:<\/strong><\/p>\n
    $<\/span> mkdir MySQLTuner-perl && cd<\/span> MySQLTuner-perl<\/span>\n$<\/span> wget http:\/\/mysqltuner.pl\/ -O mysqltuner.pl<\/span>\n$<\/span> wget https:\/\/raw.githubusercontent.com\/major\/MySQLTuner-perl\/master\/basic_passwords.txt -O basic_passwords.txt<\/span>\n$<\/span> wget https:\/\/raw.githubusercontent.com\/major\/MySQLTuner-perl\/master\/vulnerabilities.csv -O vulnerabilities.csv<\/span>\n<\/code><\/pre>\n
    In this case, you\u2019re creating a new directory for these files, and then using wget<\/code> to download the relevant files, including the mysqltuner.pl<\/code> script itself, a text file of vulnerable passwords, and a list of vulnerabilities.<\/p>\n
    Whichever method you chose, you\u2019re now ready to run the script.<\/p>\n
    $<\/span> perl mysqltuner.pl<\/span>\n<\/code><\/pre>\n
    You can also enable the CVE vulnerabilities with the following:<\/p>\n
    $<\/span> perl mysqltuner.pl --cvefile=vulnerabilities.csv<\/span>\n<\/code><\/pre>\n
    When mysqltuner.pl<\/code> is finished running, it will give you any number of recommendations about how you can improve your MySQL configuration, whether it\u2019s security-based on for superior performance. That said, it\u2019s important to reiterate the warning that the tuner\u2019s developers have included in the project\u2019s README<\/code>.<\/p>\n
    It is extremely important for you to fully understand each change you make to a MySQL database server. If you don\u2019t understand portions of the script\u2019s output, or if you don\u2019t understand the recommendations, you should consult a knowledgeable DBA or system administrator that you trust. Always test your changes on staging environments, and always keep in mind that improvements in one area can negatively affect MySQL in other areas.<\/p><\/blockquote>\n
    It\u2019s also possible to run mysqltuner.pl<\/code> on a database running inside of a Docker container\u2014perhaps useful if you followed our previous Docker tutorials<\/a> that focus on WordPress. For example, here\u2019s the results of a quick scan I did on one of those WordPress databases on my testing server.<\/p>\n
    $ perl mysqltuner.pl --host 127.0<\/span>.0<\/span>.1<\/span> --forcemem 8000<\/span> --user root --pass \u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\n >>  MySQLTuner 1.7<\/span>.2<\/span> - Major Hayden <major@mhtx.net>\n >>  Bug reports, feature requests, and<\/span> downloads at http:\/\/m<\/span>ysqltuner.com\/\n >>  Run with '--help'<\/span> for<\/span> additional options and<\/span> output filtering\n\n[--] Skipped version check for<\/span> MySQLTuner script\n[--] Performing tests on<\/span> 127.0<\/span>.0<\/span>.1<\/span>:3306<\/span>\n[OK] Logged in<\/span> using credentials passed on<\/span> the command line\n[--] Assuming 8000<\/span> MB of<\/span> physical memory\n[!!] Assuming 0<\/span> MB of<\/span> swap space (use --forceswap to specify)\n[OK] Currently running supported MySQL version 5.7<\/span>.18<\/span>\n[OK] Operating on<\/span> 64<\/span>-bit architecture\n\n-------- Log file Recommendations ------------------------------------------------------------------\n[--] Log file: stderr(0<\/span>B)\n[!!] Log file stderr doesn't exist\n[!!] Log file stderr isn'<\/span>t readable.\n\n-------- Storage Engine Statistics -----------------------------------------------------------------\n[--] Status: +ARCHIVE +BLACKHOLE +CSV -FEDERATED +InnoDB +MEMORY +MRG_MYISAM +MyISAM +PERFORMANCE_SCHEMA\n[--] Data in<\/span> InnoDB tables: 16<\/span>K (Tables: 1<\/span>)\n[OK] Total fragmented tables: 0<\/span>\n\n-------- Security Recommendations ------------------------------------------------------------------\n[OK] There are no<\/span> anonymous accounts for<\/span> any database users\n[OK] All database users have passwords assigned\n[!!] User 'wordpress@%'<\/span> has user name as<\/span> password.\n[!!] User 'root@%'<\/span> hasn't specific host restriction.\n[!!] User '<\/span>wordpress@%' hasn'<\/span>t specific host restriction.\n[--] There are 612<\/span> basic passwords in<\/span> the list.\n\n-------- CVE Security Recommendations --------------------------------------------------------------\n[OK] NO SECURITY CVE FOUND FOR YOUR VERSION\n\n-------- Performance Metrics -----------------------------------------------------------------------\n[--] Up for: 32<\/span>s (19<\/span> q [0.594<\/span> qps], 12<\/span> conn, TX: 43<\/span>K, RX: 1<\/span>K)\n[--] Reads \/ Writes: 100<\/span>% \/ 0<\/span>%\n[--] Binary logging is<\/span> disabled\n[--] Physical Memory     : 7.8<\/span>G\n[--] Max MySQL memory    : 338.9<\/span>M\n[--] Other process memory: 202.5<\/span>M\n[--] Total buffers: 169.0<\/span>M global<\/span> + 1.1<\/span>M per thread (151<\/span> max threads)\n[--] P_S Max memory usage: 72<\/span>B\n[--] Galera GCache Max memory usage: 0<\/span>B\n[OK] Maximum reached memory usage: 170.1<\/span>M (2.13<\/span>% of<\/span> installed RAM)\n[OK] Maximum possible memory usage: 338.9<\/span>M (4.24<\/span>% of<\/span> installed RAM)\n[OK] Overall possible memory usage with other process is<\/span> compatible with memory available\n[OK] Slow queries: 0<\/span>% (0<\/span>\/19<\/span>)\n[OK] Highest usage of<\/span> available connections: 0<\/span>% (1<\/span>\/151<\/span>)\n[!!] Aborted connections: 8.33<\/span>%  (1<\/span>\/12<\/span>)\n[!!] Query cache may be disabled by<\/span> default<\/span> due to mutex contention.\n[!!] Query cache efficiency: 0.0<\/span>% (0<\/span> cached \/ 8<\/span> selects)\n[OK] Query cache prunes per day: 0<\/span>\n[OK] No Sort requiring temporary tables\n[OK] No joins without indexes\n[OK] Temporary tables created on<\/span> disk: 15<\/span>% (10<\/span> on<\/span> disk \/ 66<\/span> total)\n[OK] Thread cache hit rate: 91<\/span>% (1<\/span> created \/ 12<\/span> connections)\n[OK] Table cache hit rate: 93<\/span>% (102<\/span> open \/ 109<\/span> opened)\n[OK] Open file limit used: 0<\/span>% (14<\/span>\/65<\/span>K)\n[OK] Table locks acquired immediately: 100<\/span>% (102<\/span> immediate \/ 102<\/span> locks)\n\n-------- Performance schema ------------------------------------------------------------------------\n[--] Memory used by<\/span> P_S: 72<\/span>B\n[--] Sys schema is<\/span> installed.\n\n-------- ThreadPool Metrics ------------------------------------------------------------------------\n[--] ThreadPool stat is<\/span> disabled.\n\n-------- MyISAM Metrics ----------------------------------------------------------------------------\n[!!] Key buffer used: 18.3<\/span>% (1<\/span>M used \/ 8<\/span>M cache)\n[OK] Key buffer size \/ total MyISAM indexes: 8.0<\/span>M\/43.0<\/span>K\n[!!] Read Key buffer hit rate: 50.0<\/span>% (6<\/span> cached \/ 3<\/span> reads)\n\n-------- InnoDB Metrics ----------------------------------------------------------------------------\n[--] InnoDB is<\/span> enabled.\n[--] InnoDB Thread Concurrency: 0<\/span>\n[OK] InnoDB File per table is<\/span> activated\n[OK] InnoDB buffer pool \/ data size: 128.0<\/span>M\/16.0<\/span>K\n[!!] Ratio InnoDB log file size \/ InnoDB Buffer pool size (75<\/span> %): 48.0<\/span>M * 2<\/span>\/128.0<\/span>M should be equal 25<\/span>%\n[OK] InnoDB buffer pool instances: 1<\/span>\n[--] Number of<\/span> InnoDB Buffer Pool Chunk : 1<\/span> for<\/span> 1<\/span> Buffer Pool Instance(s)\n[OK] Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size & Innodb_buffer_pool_instances\n[!!] InnoDB Read buffer efficiency: 82.53<\/span>% (1176<\/span> hits\/ 1425<\/span> total)\n[!!] InnoDB Write Log efficiency: 0<\/span>% (2<\/span> hits\/ 0<\/span> total)\n[OK] InnoDB log waits: 0.00<\/span>% (0<\/span> waits \/ 2<\/span> writes)\n\n-------- AriaDB Metrics ----------------------------------------------------------------------------\n[--] AriaDB is<\/span> disabled.\n\n-------- TokuDB Metrics ----------------------------------------------------------------------------\n[--] TokuDB is<\/span> disabled.\n\n-------- XtraDB Metrics ----------------------------------------------------------------------------\n[--] XtraDB is<\/span> disabled.\n\n-------- RocksDB Metrics ---------------------------------------------------------------------------\n[--] RocksDB is<\/span> disabled.\n\n-------- Spider Metrics ----------------------------------------------------------------------------\n[--] Spider is<\/span> disabled.\n\n-------- Connect Metrics ---------------------------------------------------------------------------\n[--] Connect is<\/span> disabled.\n\n-------- Galera Metrics ----------------------------------------------------------------------------\n[--] Galera is<\/span> disabled.\n\n-------- Replication Metrics -----------------------------------------------------------------------\n[--] Galera Synchronous replication: NO\n[--] No replication slave(s) for<\/span> this<\/span> server.\n[--] This is<\/span> a standalone server.\n\n-------- Recommendations ---------------------------------------------------------------------------\nGeneral recommendations:\n    Set up a Secure Password for<\/span> user@host ( SET PASSWORD FOR 'user'<\/span>@'SpecificDNSorIp'<\/span> = PASSWORD('secure_password'<\/span>); )\n    Restrict Host for<\/span> user@% to user@SpecificDNSorIp\n    MySQL started within last 24<\/span> hours - recommendations may be inaccurate\n    Reduce or<\/span> eliminate unclosed connections and<\/span> network issues\nVariables to adjust:\n    query_cache_size (=0<\/span>)\n    query_cache_type (=0<\/span>)\n    query_cache_limit (> 1<\/span>M, or<\/span> use smaller result sets)\n    innodb_log_file_size * innodb_log_files_in_group should be equal to 1<\/span>\/4<\/span> of<\/span> buffer pool size (=64<\/span>M) if<\/span> possible.\n<\/code><\/pre>\n
    As you can see, there are a number of security improvements for me to follow up on, and some variables I can change to improve performance.<\/p>\n
    <\/a>Additional options and resources<\/h2>\n
    There are other caching layers that exist on the server itself (such as memcached), rather than a CDN like Cloudflare, but setting those up are beyond the scope of this tutorial.<\/p>\n
    <\/a>Option 3. Cloudflare<\/h2>\n
    The previous two recommendations have been all about improving the performance of MySQL queries, but what about reducing queries in the first place? Many websites, such as a personal blog or portfolio, don\u2019t actually change all that often. This means it should be possible to serve a static HTML version of the site instead of having every visitor query the database for every loaded page.<\/p>\n
    Cloudflare is the most popular solution to placing a caching layer between your user and the database. It\u2019s global content delivery network (CDN) is one of the fastest out there, which means your website will not only load faster, but it will rely on your database less than ever. Plus, if your site goes down, Cloudflare will try to serve its cached version rather than show an error.<\/p>\n
    For WordPress users, there\u2019s even a plugin to make that process easier than ever. It doesn\u2019t make sense to simply duplicate the process that Cloudflare has put together on their own support pages, so we recommend you go checkout their Using Cloudflare with WordPress<\/a> page for more information.<\/p>\n
    For other applications, it\u2019s also possible to use the free tier of Cloudflare as a caching layer as well. In that case, you need to point your domain to Cloudflare\u2019s nameservers, and then point Cloudflare\u2019s DNS to your server\u2019s IP.<\/p>\n