Exabytes WordPress Slow TTFB: MyISAM to InnoDB Fix
Fix excruciatingly slow database queries on Exabytes by converting legacy MyISAM WordPress tables to InnoDB and tuning the buffer pool.
Why Your Database Queries Are Timing Out
If your WordPress backend on Exabytes is crawling and your Time to First Byte (TTFB) is over 2 seconds, the issue is often database locking.
Older WordPress installations (or databases created by legacy auto-installers) default to the MyISAM storage engine. MyISAM uses table-level locking. If one user is updating their WooCommerce cart (writing to a table), every other user trying to read that table must wait in a queue.
The modern standard is InnoDB, which uses row-level locking, allowing concurrent reads and writes.
1. Checking Your Storage Engine
Log into phpMyAdmin via cPanel, select your database, and look at the "Type" column. If you see MyISAM across wp_posts or wp_options, you need to migrate.
Via SSH/MySQL CLI:
SELECT TABLE_NAME, ENGINE FROM information_schema.TABLES WHERE TABLE_SCHEMA = 'your_database_name';
2. Converting Tables to InnoDB
Before proceeding, take a full SQL backup.
To convert a table via SQL:
ALTER TABLE wp_posts ENGINE=InnoDB;
ALTER TABLE wp_options ENGINE=InnoDB;
If you have SSH access, you can use WP-CLI to generate the queries for all tables:
wp db query "SELECT CONCAT('ALTER TABLE ', TABLE_NAME, ' ENGINE=InnoDB;') FROM information_schema.TABLES WHERE TABLE_SCHEMA = 'your_database' AND ENGINE = 'MyISAM';" --skip-column-names > convert.sql
mysql your_database < convert.sql
3. Tuning the InnoDB Buffer Pool (VPS only)
If you are on an Exabytes VPS, InnoDB requires memory tuning to be fast. Edit /etc/my.cnf or /etc/mysql/my.cnf:
# Set to 50-70% of total server RAM
innodb_buffer_pool_size = 2G
innodb_log_file_size = 512M
Restart MySQL: systemctl restart mysql or systemctl restart mariadb.
Is database latency killing your conversion rate? We migrated and optimized the database layer for Trexon Energy, dropping TTFB from 3 seconds to under 200ms.
Stop losing customers to slow load times. Let JagaWeb optimize your data layer with our RM5,000 Ownership & Access Review, and keep it highly tuned with our RM450/month Care Plan.
Ready to verify who owns your website?
Replace uncertainty with a decision-ready ownership and access report. The fixed Ownership & Access Review is RM1,500 before SST and includes a 30-day action plan.