Avoid These 65 Slow Loading WordPress Plugins

Which Plugin Is Slowing Down Your WordPress Website?

I’ve been using WordPress for a very long time and tested hundreds of WordPress plugins. Below is a list of slow loading plugins that will slow down your website.

Note that I have personally tested the below plugins and your experience with these plugins my differ from my personal results with the below plugins so feel free to let me know.

After getting rid of slow plugins on my blog. My blog now loads in under 2 seconds. The slow plugins like Contact Form 7 and Contextual Related Posts that I still use on my blog I use the Asset Clean Up plugin to trim the bloat and fat (unnecessary CSS/Javascript) from my site.

Hot Tip: Your website’s speed and loading time will become a huge ranking factor in 2021(Google said so themselves) so be sure to get your website ready when the Google algorithm hits in 2021.

Unique/Great content will still dominate the serps though! so don’t lose focus of that. It’s just that Google will put heavy emphasis on the user experience and page loading times in conjunction with great content.

So just imagine having keyword rich, SEO optimized pages along with a fast website = money in the bank! Anyways back to the slow plugins… that’s why you are here right?

You can see below my blog’s loading time from using the GTmetrix tool along with my Google Page Speed Insight scores for both Desk top and Mobile users. (Removing bloated plugins was a huge factor.)

1. My GTmetrix Page Speed/Y Slow Scores: 99%/93% and fully load of 1.2 seconds.

2. My Desktop Page Speed Insights Scores 100

3. My Mobile Page Speed Insights Scores 94

Oh yes before I forget to tell you I also use the WP Rocket plugin on my blog that has also helped me achieve those fast load times and scores with my blog.
SEMrush

(Note: it’s a premium/paid plugin no free version, but Autoptimze plugin is a great free alternative to WP Rocket if you’re strapped for cash.)

List of 65 Slow Plugins I’ve tested…

  1. AddThis
  2. AdSense Click Fraud Monitoring
  3. All-In-One Event Calendar
  4. Backup Buddy
  5. Beaver Builder
  6. Better WordPress Google XML Sitemaps
  7. Broken Link checker (use Dr. Link Check)
  8. Constant Contact for WordPress
  9. Contact Form 7 ( I still use this with Asset clean up )
  10. Contextual Related Posts ( I still use this with text only )
  11. Digi Auto Links
  12. Disqus Comment System
  13. Divi Builder
  14. Essential Grid
  15. Facebook Chat
  16. Fancy Gallery
  17. Fuzzy SEO Booster
  18. Google Analytics
  19. Google Language Translator
  20. Google Translate
  21. Google XML Sitemaps
  22. Jetpack
  23. Leaflet Maps Marker
  24. MyReview
  25. NextGEN Gallery
  26. NewStatPress
  27. Real Estate Website Builder
  28. Really Simple Share
  29. Reveal IDs
  30. Revolution Slider
  31. Sharebar
  32. ShareThis
  33. S2 member
  34. SEO Auto Links & Related Posts
  35. Share Buttons by AddToAny
  36. Share Buttons by E-MAILiT
  37. ShareThis
  38. Social Discussions
  39. Socialable
  40. Similar Posts
  41. Slimstat Analytics
  42. SumoMe
  43. Talk.To
  44. Tribulent Slideshow Gallery
  45. Ultimate Social Media & Share
  46. VaultPress
  47. WooCommerce Customer History
  48. Wordfence (disable live traffic reports)
  49. WordPress Facebook
  50. WordPress Related Posts
  51. WordPress Popular Posts
  52. WordPress Social Ring
  53. WP Bakey (formerly Visual Composer)
  54. WP Facebook Like Plugin
  55. WP Jump Menu
  56. WP Social Bookmarking Lite
  57. WP Social Share
  58. WP Statistics
  59. WP Power Stats
  60. WP-PostViews
  61. WPML (if you use too many extensions)
  62. WPCloaker
  63. WPML
  64. Yet Another Related Post Plugin
  65. Yuzo Related Posts

Okay, so now that I’ve hammered home that popular plugins might also be the reason your site is running slowly…what do you actually do about it?

If you’re using any of the plugins on the above list, either get rid of them or find a replacement. If it’s a must use the Asset Clean Up plugin to strip unnecessary code from loading on your website post/pages.

Is there any other slow plugins you’ve encountered?

Let me know if there is a recommendation for me to replace Contact Form 7 and Contextual Related Post plugins with a lighter plugin then do let me know.

 

magento2 – Load times for files in pub/static/ are extremely variable and often painfully slow

On Magento 2.3.3 I’m seeing extremely variable load times for files served from Magento’s pub/static directory. This happens in both developer and production modes, and I can’t understand what’s causing it.

Main symptoms are pages which take a huge amount of time to load, especially on first visit and especially when the FPC is disabled. But I don’t just mean “a few seconds extra” – I’m talking minutes of load time.

pub/static resources (mainly JS files) take several seconds each to reach TTFB i.e. there’s tons of “waiting” for files in the browser. This causes a massive amount of request blocking as the browser waits.

Even if I load up the URI of a single JS file in the browser the load times are insanely variable: first time I request a file directly it might take 4 seconds to load, then I refresh a couple of times and it loads instantly, then I refresh again and it’s back to 4-5 seconds. And this is on a machine which has zero net traffic other than my own testing.

The hardware I’m using is a 32-core CentOS-based machine with 128GB RAM and SSDs so this should not be a hardware issue. I’m running httpd, MariaDB, php-fpm, redis/memcache for page cache and session storage. I’ve set up Varnish in the past but would prefer to get Magento running acceptably before resorting to using aggressive caching as a crutch.

My php-fpm config looks like this:

listen = /var/run/php-fpm/website.sock
listen.owner = magento
listen.group = www
listen.mode = 0660
user = magento
group = www
pm = static
pm.max_children = 500
pm.start_servers = 30
pm.min_spare_servers = 30
pm.max_spare_servers = 50
pm.max_requests = 500
php_admin_flag(log_errors) = on
php_admin_flag(zlib.output_compression) = On
php_value(memory_limit) = "4096M"
php_value(session.gc_maxlifetime) = "86400"
php_value(opcache.memory_consumption) = 512MB
php_value(opcache.max_accelerated_files) = 60000
php_value(opcache.consistency_checks) = 0
php_value(opcache.revalidate_freq) = 0
php_value(opcache.enable_cli) = 1
php_value(opcache.interned_strings_buffer) = 64

Any ideas?

How to fix iPhone X + iOS 13 Slow Wifi?

How do I fix slow wifi on an iPhone XR (iOS 13.4.1)?

The boss has an iPhone XR (iOS 13.4.1), and I have an iPhone 6 (iOS 12.4.5). The iPhone 6 gets 100% better Mbps throughput around my house. I have validated my router health and validated network setup on both phones. I have done all the reset/forget network cycling recommended by guides like this and this and this.

I measure the same performance percentage difference–iPhone 6 performs roughly 110% better–in all these tested scenarios:

  • 802.11 b/g/n 2.4 GHz network connection on both phones, simultaneously
  • 802.11 ac 5 GHz network connection on both phones, simultaneously (first screenshot)
  • Bluetooth off (second screenshot)

My test was:

  1. hold both phones in hand
  2. test average Mbps download speeds using Wi-Fi Sweetspots app
  3. average over ~10 seconds
  4. test 6 different spots around the house
  5. record results

Here are the side-by-side results of the latter two tests; left side is iPhone XR + iOS 13.4.1, right side is iPhone 6 + iOS 12.4.5

test on 5GHz AC network

Test with bluetooth radio off on both phones:

enter image description here

In both tests, “Spot 4” is standing directly next to the Wifi router.

magento2 – Rest API Requests are too slow

We are using the third party vendor for stock & product management.

They are updating the custom attributes in Magento 2 using Rest API calls.

for example:

PUT index.php/rest/all/V1/products/{PRODUCTSKU}
Data sent = {“product”:{“custom_attributes”:[{“attribute_code”:”custom_attribute_code”,”value”:”123456789″}]}}

This request takes around 8-10 seconds to get the response.

It takes more than 1 hour to update 500 records.

Can you please suggest how to imporve this response time.

Network manager slow to connect

On Kubuntu 20.04 the NetworkManager is slow to connect via LAN. It is in the “Setting network address” state for about 20-30 seconds, while dhclient from console connects (obtains IP) immediately. I’m not sure what other info to include, which log files etc. to post to help resolve this. Please advice.

firebase – Firestore operations in Cloud functions slow compared to web client

I haven’t found much information online about that issue, and it feels like I’m the only user experiencing this.
I read a few comments about how people measure performance and I’ve included the code and measurements results below.

I’m testing 3 operations to Firestore:

  • Read
  • Write
  • onSnapshot (time between write call and notification of
    change)

On 3 environments: web client, emulator, cloud functions production (nodejs10).

Performance from a web client is really good, instant.
Emulator is great, instant (see results below).

Production is slow, and the numbers are curiously rounded.

  • Read: 3700ms
  • Write: 2900ms
  • Snapshot: 2704ms

And this is after the infamous cold start.

Am I missing something obvious here?

Code:

function epochms() {
  return Math.floor(new Date());
}

async function run10Times() {
  for (var i = 0; i < 10; ++i)
    await updateRecord("Tests/manager/Updates", i.toString().padStart(2, '0'));
}

async function updateRecord(colpath, id) {
  // Cold start
  let obj = {id};
  let startRead = epochms();
  await db.collection("Tests").doc("manager").get();
  let startWrite = epochms();
  await db.collection(colpath).doc(obj.id).set({startRead, endRead:startWrite, startWrite});
  let endWrite = epochms();
  await db.collection(colpath).doc(obj.id).update({endWrite});
  // Set on Snapshot
  db.collection(colpath).doc(obj.id).onSnapshot(async (doc) => {
    log.log(`(${id}) test.onSnapshot`);
    let snapshotReceived = epochms();
    obj = { id:doc.id, ...doc.data() };
    if (obj.snapshotStarted && !obj.snapshotReceived)
      await db.collection(colpath).doc(obj.id).update({snapshotReceived});
    else 
      log.log(`(${id}) test.onSnapshot late, ignore`);
  });
  let snapshotStarted = epochms();
  await db.collection(colpath).doc(obj.id).update({snapshotStarted});
}

exports.emulatorScheduledEventUpdate = functions.https.onCall(() => {
  run10Times();
  return 0;
});

Output in cloud functions

00
Read: 91192ms
Write: 5301ms
Snapshot: 16000ms

01
Read: 12400ms
Write: 2700ms
Snapshot: 4501ms

02
Read: 4201ms
Write: 2700ms
Snapshot: 3901ms

03
Read: 4301ms
Write: 900ms
Snapshot: 3300ms

04
Read: 4599ms
Write: 1901ms
Snapshot: 4901ms

05
Read: 4400ms
Write: 2302ms
Snapshot: 2700ms

06
Read: 4200ms
Write: 900ms
Snapshot: 2396ms

07
Read: 4900ms
Write: 1099ms
Snapshot: 4602ms

08
Read: 2300ms
Write: 1500ms
Snapshot: 2500ms

09
Read: 3300ms
Write: 1900ms
Snapshot: 2400ms

Output in emulator

00
Read: 238ms
Write: 27ms
Snapshot: 18ms

01
Read: 7ms
Write: 13ms
Snapshot: 17ms

02
Read: 5ms
Write: 12ms
Snapshot: 12ms

03
Read: 5ms
Write: 16ms
Snapshot: 16ms

04
Read: 4ms
Write: 24ms
Snapshot: 18ms

05
Read: 4ms
Write: 26ms
Snapshot: 16ms

06
Read: 4ms
Write: 31ms
Snapshot: 20ms

07
Read: 6ms
Write: 28ms
Snapshot: 17ms

08
Read: 5ms
Write: 34ms
Snapshot: 26ms

09
Read: 5ms
Write: 10ms
Snapshot: 18ms

Thanks,

synchronization – Sync with bitcoin-qt very slow (0,01%)

Bitcoin Core is capable of full sync in a relatively short period of time depending mainly on the hardware.

Most of the work done is not actually downloading the blocks, it is validating them and every transaction that they contain. It not only depends on downloading the blocks but also on the quantity and complexity of every transaction. The downloading of the blocks themselves is usually not an issue if you are connected (outbound) to several nodes. I am able to download blocks generally in forty-five seconds each (which includes the request time etc. and validation as well as the transfer) when I have been offline and am catching up on my restricted local 256Kbps link. My upload speed is low, and latency is high. At the rate of one block per forty-five seconds, it would currently take over two-hundred-and-sixty-three days to complete the whole blockchain as there are more than 506822 blocks as of writing.

From my personal experience, the initial sync actually took over five days to complete on a 2.5GHz Core i5 notebook with 4GB of RAM running Fedora with Bitcoin Core v0.15.1. For that, I used ADSL2+ and never perceived the actual downloading of the blocks to be the issue.

Performance of initial sync

Performance of initial sync largely comes down to the individual performance of your computer, provided your internet is fine.

Always use the latest release version of Bitcoin Core (includes bitcoin-qt and bitcoind) downloaded from the official site at www.bitcoin.org. An upgrade is safe and easy, just safely exit Bitcoin Core first and make a new secure backup of your wallet.dat before you upgrade.

Adjusting parameters

There are some parameters that you can look at and consider depending on your system. Always make a backup of your wallet before making any changes. The parameters can be entered at the command line or generally in your bitcoin.conf file, which you would need to exit and restart Bitcoin Core in that case to see the effect. Some things to consider that could make a difference:

I am presuming here that you are running bitcoin-qt which is the GUI version and not bitcoind.

If parameters are used in the bitcoin.conf file, omit the leading -.

  • -datadir= You could have your datadir on a fast drive. If you move your whole .bitcoin folder you will need to specify this parameter on the command line. Note that if you change your datadir and do not copy the .bitcoin folder over to the new location first, it will create a new wallet and begin downloading the blockchain again from the start.
  • -dbcache= The default for this is 450. If you have 8GB of RAM, you could easily set this to 4096
  • par= The default for this setting is auto, but I do not know what the automatic setting does. You could try setting this to -1 which leaves one core free.
  • -banscore= You could try setting this to 10 to kick off misbehaving nodes sooner.
  • -listen= You could temporarily set this to 0 to disable incoming connections while you get the initial sync done. Your busy node does not need the additional work.

After the initial sync, you can revert these settings to their defaults but probably leave your datadir wherever you put it.

Some of these parameters are available as options in the bitcoin-qt Settings > Options menu.

TLDR; The short answer if you want it fast is, get a fast computer, loads of RAM, a fast HDD and, fast internet. The same as anytime you want anything fast on a computer.

In the real world, and from personal experience, using an SSD increased sync speed more than 10x on my example system from the performance noted above.

Anecdotes

Real life example of varying system performance: I know someone personally who had to work on a quite large, but not extraordinarily large, Illustrator file. He opened it on his ~12-month-old upper spec Mac which usually performs great and, it was virtually unusable (slow to respond). Just for kicks he thought he would try the same file on a bog standard PC, opened it in Illustrator and it was completely normal. Some hardware/software builds have bottlenecks for some processes. The opposite result is probably true for some operations.

Also note, I have observed that exiting and restarting Bitcoin Core during initial sync seems to speed it up a bit for a while once it connects to nodes again.

Referencing again personal experience, syncing on Windows 10 64-bit seems to be orders of magnitude faster than syncing on Linux on the same hardware – even if Windows is running in Gnome-Boxes, it easily churns through 100 blocks per second during the initial stages of download.

Alternatives

If you are in serious trouble waiting to sync Bitcoin Core (a full node client) and you do not need the additional features that Bitcoin Core provides then, you may consider trying Electrum (not a full node client) which does not need to do the initial sync. On Fedora 27, getting Electrum is as simple as sudo dnf install electrum.

How I debug a mongodb slow regex query?

I have two simple queries on a collection of 22 millions documents.

query 1:

db.audits.find({"w.em": /^name.lastname/i})

return in less than 1 second.

query 2:

db.audits.find({"w.d": /^name.lastname/i})

it runs for more than 30seconds (and rightly not found results).

The only difference on the two queries is the field I am searching on. Both fields are indexed, you can find here the explain for both : it is identical!

How can the queries perform so differently??

I am on mongodb 3.4.23

Xubuntu 20.04 suddenly very slow

Upgraded to 20.04 about a month ago. The file manager opened slowly, browsers open slowly, etc. Two days ago the system became intolerably slow. How to reinstall Xubuntu 20.04? The system just hung again for 15 seconds between typing “Xubuntu” and “20.04” Sporadic hang up in every application I try to run such as Parole Media Player playing a file from disk and VLC hanging up so I had to kill it from the terminal.

mysql – Slow Database with concurrent queries, Table cache hitrate 0% [Newbie! Need help :)]

I’m a bit of a newbie when it comes to dba work so please take it easy!

I have gone through countless threads trying to improve the performance of my database, looking for someone who could give me some pointers on changes I may need to do for my variables that may squeeze more performance.
Or if I have misconfigured anything.

Here are the details
Server specs: E3 1270 V6 w/32gb Ram
OS: Windows Server 2016
Mysql Version: 8.0.19 – MySQL Community Server – GPL

MYSQL Config
https://ybin.me/p/b99f994ad62c27ad#zvwS1+XGP6ZIZtKYdiMOySg+aYR85Qp3ciTvFr6q4mE=

Show Global Status (during high usage):

https://ybin.me/p/b74fae252e807749#F9+88tWsVo/hqHjKlnlnG1gEUwj7vlonLlYrUxXnThg=

SHOW ENGINE INNODB STATUS (During High Usage)

InnoDB      
=====================================
2020-05-17 16:57:16 0xa6c INNODB MONITOR OUTPUT
=====================================
Per second averages calculated from the last 7 seconds
-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 103908 srv_active, 0 srv_shutdown, 300397 srv_idle
srv_master_thread log flush and writes: 0
----------
SEMAPHORES
----------
OS WAIT ARRAY INFO: reservation count 42855
OS WAIT ARRAY INFO: signal count 37923
RW-shared spins 3053, rounds 3116, OS waits 59
RW-excl spins 6909, rounds 59455, OS waits 1320
RW-sx spins 99, rounds 1306, OS waits 25
Spin rounds per wait: 1.02 RW-shared, 8.61 RW-excl, 13.19 RW-sx
------------------------
LATEST DETECTED DEADLOCK
------------------------
2020-05-17 13:52:00 0x2904
*** (1) TRANSACTION:
TRANSACTION 12175899, ACTIVE 0 sec starting index read
mysql tables in use 3, locked 3
LOCK WAIT 4 lock struct(s), heap size 1136, 3 row lock(s)
MySQL thread id 3340, OS thread handle 3660, query id 2398670 localhost 127.0.0.1 root updating
UPDATE user_inventory SET count = 22 WHERE identifier = 'steam:11000013f8eef2a' AND item = 'bandage'

*** (1) HOLDS THE LOCK(S):
RECORD LOCKS space id 584 page no 84 n bits 336 index PRIMARY of table `essentialmode`.`user_inventory` trx id 12175899 lock_mode X locks rec but not gap
Record lock, heap no 69 PHYSICAL RECORD: n_fields 6; compact format; info bits 0
 0: len 4; hex 8039a49f; asc  9  ;;
 1: len 6; hex 000000b9849a; asc       ;;
 2: len 7; hex 02000001ad0151; asc       Q;;
 3: len 21; hex 737465616d3a313130303030313366386565663261; asc steam:11000013f8eef2a;;
 4: len 7; hex 62616e64616765; asc bandage;;
 5: len 4; hex 8000002b; asc    +;;


*** (1) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 584 page no 2445 n bits 792 index item of table `essentialmode`.`user_inventory` trx id 12175899 lock_mode X waiting
Record lock, heap no 561 PHYSICAL RECORD: n_fields 2; compact format; info bits 0
 0: len 7; hex 62616e64616765; asc bandage;;
 1: len 4; hex 800002e8; asc     ;;


*** (2) TRANSACTION:
TRANSACTION 12175886, ACTIVE 0 sec fetching rows
mysql tables in use 3, locked 3
LOCK WAIT 60 lock struct(s), heap size 8400, 2334 row lock(s)
MySQL thread id 3336, OS thread handle 10296, query id 2398648 localhost 127.0.0.1 root updating
UPDATE user_inventory SET count = 4 WHERE identifier = 'steam:11000010e1c050e' AND item = 'bandage'

*** (2) HOLDS THE LOCK(S):
RECORD LOCKS space id 584 page no 2445 n bits 792 index item of table `essentialmode`.`user_inventory` trx id 12175886 lock_mode X
Record lock, heap no 1 PHYSICAL RECORD: n_fields 1; compact format; info bits 0
 0: len 8; hex 73757072656d756d; asc supremum;;

Record lock, heap no 561 PHYSICAL RECORD: n_fields 2; compact format; info bits 0
 0: len 7; hex 62616e64616765; asc bandage;;
 1: len 4; hex 800002e8; asc     ;;


*** (2) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 584 page no 84 n bits 336 index PRIMARY of table `essentialmode`.`user_inventory` trx id 12175886 lock_mode X locks rec but not gap waiting
Record lock, heap no 69 PHYSICAL RECORD: n_fields 6; compact format; info bits 0
 0: len 4; hex 8039a49f; asc  9  ;;
 1: len 6; hex 000000b9849a; asc       ;;
 2: len 7; hex 02000001ad0151; asc       Q;;
 3: len 21; hex 737465616d3a313130303030313366386565663261; asc steam:11000013f8eef2a;;
 4: len 7; hex 62616e64616765; asc bandage;;
 5: len 4; hex 8000002b; asc    +;;

*** WE ROLL BACK TRANSACTION (1)
------------
TRANSACTIONS
------------
Trx id counter 12207888
Purge done for trx's n:o < 12207888 undo n:o < 0 state: running but idle
History list length 19
LIST OF TRANSACTIONS FOR EACH SESSION:
---TRANSACTION 283609840283040, not started
0 lock struct(s), heap size 1136, 0 row lock(s)
---TRANSACTION 283609840282192, not started
0 lock struct(s), heap size 1136, 0 row lock(s)
---TRANSACTION 283609840281344, not started
0 lock struct(s), heap size 1136, 0 row lock(s)
--------
FILE I/O
--------
I/O thread 0 state: wait Windows aio (insert buffer thread)
I/O thread 1 state: wait Windows aio (log thread)
I/O thread 2 state: wait Windows aio (read thread)
I/O thread 3 state: wait Windows aio (read thread)
I/O thread 4 state: wait Windows aio (read thread)
I/O thread 5 state: wait Windows aio (read thread)
I/O thread 6 state: wait Windows aio (read thread)
I/O thread 7 state: wait Windows aio (read thread)
I/O thread 8 state: wait Windows aio (read thread)
I/O thread 9 state: wait Windows aio (read thread)
I/O thread 10 state: wait Windows aio (read thread)
I/O thread 11 state: wait Windows aio (read thread)
I/O thread 12 state: wait Windows aio (read thread)
I/O thread 13 state: wait Windows aio (read thread)
I/O thread 14 state: wait Windows aio (read thread)
I/O thread 15 state: wait Windows aio (read thread)
I/O thread 16 state: wait Windows aio (read thread)
I/O thread 17 state: wait Windows aio (read thread)
I/O thread 18 state: wait Windows aio (read thread)
I/O thread 19 state: wait Windows aio (read thread)
I/O thread 20 state: wait Windows aio (read thread)
I/O thread 21 state: wait Windows aio (read thread)
I/O thread 22 state: wait Windows aio (read thread)
I/O thread 23 state: wait Windows aio (read thread)
I/O thread 24 state: wait Windows aio (read thread)
I/O thread 25 state: wait Windows aio (read thread)
I/O thread 26 state: wait Windows aio (read thread)
I/O thread 27 state: wait Windows aio (read thread)
I/O thread 28 state: wait Windows aio (read thread)
I/O thread 29 state: wait Windows aio (read thread)
I/O thread 30 state: wait Windows aio (read thread)
I/O thread 31 state: wait Windows aio (read thread)
I/O thread 32 state: wait Windows aio (read thread)
I/O thread 33 state: wait Windows aio (read thread)
I/O thread 34 state: wait Windows aio (read thread)
I/O thread 35 state: wait Windows aio (read thread)
I/O thread 36 state: wait Windows aio (read thread)
I/O thread 37 state: wait Windows aio (read thread)
I/O thread 38 state: wait Windows aio (read thread)
I/O thread 39 state: wait Windows aio (read thread)
I/O thread 40 state: wait Windows aio (read thread)
I/O thread 41 state: wait Windows aio (read thread)
I/O thread 42 state: wait Windows aio (read thread)
I/O thread 43 state: wait Windows aio (read thread)
I/O thread 44 state: wait Windows aio (read thread)
I/O thread 45 state: wait Windows aio (read thread)
I/O thread 46 state: wait Windows aio (read thread)
I/O thread 47 state: wait Windows aio (read thread)
I/O thread 48 state: wait Windows aio (read thread)
I/O thread 49 state: wait Windows aio (read thread)
I/O thread 50 state: wait Windows aio (read thread)
I/O thread 51 state: wait Windows aio (read thread)
I/O thread 52 state: wait Windows aio (read thread)
I/O thread 53 state: wait Windows aio (read thread)
I/O thread 54 state: wait Windows aio (read thread)
I/O thread 55 state: wait Windows aio (read thread)
I/O thread 56 state: wait Windows aio (read thread)
I/O thread 57 state: wait Windows aio (read thread)
I/O thread 58 state: wait Windows aio (read thread)
I/O thread 59 state: wait Windows aio (read thread)
I/O thread 60 state: wait Windows aio (read thread)
I/O thread 61 state: wait Windows aio (read thread)
I/O thread 62 state: wait Windows aio (read thread)
I/O thread 63 state: wait Windows aio (read thread)
I/O thread 64 state: wait Windows aio (read thread)
I/O thread 65 state: wait Windows aio (read thread)
I/O thread 66 state: wait Windows aio (write thread)
I/O thread 67 state: wait Windows aio (write thread)
I/O thread 68 state: wait Windows aio (write thread)
I/O thread 69 state: wait Windows aio (write thread)
I/O thread 70 state: wait Windows aio (write thread)
I/O thread 71 state: wait Windows aio (write thread)
I/O thread 72 state: wait Windows aio (write thread)
I/O thread 73 state: wait Windows aio (write thread)
I/O thread 74 state: wait Windows aio (write thread)
I/O thread 75 state: wait Windows aio (write thread)
I/O thread 76 state: wait Windows aio (write thread)
I/O thread 77 state: wait Windows aio (write thread)
I/O thread 78 state: wait Windows aio (write thread)
I/O thread 79 state: wait Windows aio (write thread)
I/O thread 80 state: wait Windows aio (write thread)
I/O thread 81 state: wait Windows aio (write thread)
I/O thread 82 state: wait Windows aio (write thread)
I/O thread 83 state: wait Windows aio (write thread)
I/O thread 84 state: wait Windows aio (write thread)
I/O thread 85 state: wait Windows aio (write thread)
I/O thread 86 state: wait Windows aio (write thread)
I/O thread 87 state: wait Windows aio (write thread)
I/O thread 88 state: wait Windows aio (write thread)
I/O thread 89 state: wait Windows aio (write thread)
I/O thread 90 state: wait Windows aio (write thread)
I/O thread 91 state: wait Windows aio (write thread)
I/O thread 92 state: wait Windows aio (write thread)
I/O thread 93 state: wait Windows aio (write thread)
I/O thread 94 state: wait Windows aio (write thread)
I/O thread 95 state: wait Windows aio (write thread)
I/O thread 96 state: wait Windows aio (write thread)
I/O thread 97 state: wait Windows aio (write thread)
I/O thread 98 state: wait Windows aio (write thread)
I/O thread 99 state: wait Windows aio (write thread)
I/O thread 100 state: wait Windows aio (write thread)
I/O thread 101 state: wait Windows aio (write thread)
I/O thread 102 state: wait Windows aio (write thread)
I/O thread 103 state: wait Windows aio (write thread)
I/O thread 104 state: wait Windows aio (write thread)
I/O thread 105 state: wait Windows aio (write thread)
I/O thread 106 state: wait Windows aio (write thread)
I/O thread 107 state: wait Windows aio (write thread)
I/O thread 108 state: wait Windows aio (write thread)
I/O thread 109 state: wait Windows aio (write thread)
I/O thread 110 state: wait Windows aio (write thread)
I/O thread 111 state: wait Windows aio (write thread)
I/O thread 112 state: wait Windows aio (write thread)
I/O thread 113 state: wait Windows aio (write thread)
I/O thread 114 state: wait Windows aio (write thread)
I/O thread 115 state: wait Windows aio (write thread)
I/O thread 116 state: wait Windows aio (write thread)
I/O thread 117 state: wait Windows aio (write thread)
I/O thread 118 state: wait Windows aio (write thread)
I/O thread 119 state: wait Windows aio (write thread)
I/O thread 120 state: wait Windows aio (write thread)
I/O thread 121 state: wait Windows aio (write thread)
I/O thread 122 state: wait Windows aio (write thread)
I/O thread 123 state: wait Windows aio (write thread)
I/O thread 124 state: wait Windows aio (write thread)
I/O thread 125 state: wait Windows aio (write thread)
I/O thread 126 state: wait Windows aio (write thread)
I/O thread 127 state: wait Windows aio (write thread)
I/O thread 128 state: wait Windows aio (write thread)
I/O thread 129 state: wait Windows aio (write thread)
Pending normal aio reads: (0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) , aio writes: (0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) ,
 ibuf aio reads:, log i/o's:, sync i/o's:
Pending flushes (fsync) log: 0; buffer pool: 0
25639 OS file reads, 5252794 OS file writes, 2142145 OS fsyncs
0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s
-------------------------------------
INSERT BUFFER AND ADAPTIVE HASH INDEX
-------------------------------------
Ibuf: size 1, free list len 30, seg size 32, 78 merges
merged operations:
 insert 89, delete mark 3, delete 0
discarded operations:
 insert 0, delete mark 0, delete 0
Hash table size 4425293, node heap has 577 buffer(s)
Hash table size 4425293, node heap has 7 buffer(s)
Hash table size 4425293, node heap has 3 buffer(s)
Hash table size 4425293, node heap has 42 buffer(s)
Hash table size 4425293, node heap has 25 buffer(s)
Hash table size 4425293, node heap has 8 buffer(s)
Hash table size 4425293, node heap has 117 buffer(s)
Hash table size 4425293, node heap has 268 buffer(s)
63.71 hash searches/s, 4.29 non-hash searches/s
---
LOG
---
Log sequence number          8204611911
Log buffer assigned up to    8204611911
Log buffer completed up to   8204611911
Log written up to            8204611911
Log flushed up to            8204611911
Added dirty pages up to      8204611911
Pages flushed up to          8204611911
Last checkpoint at           8204611911
2113740 log i/o's done, 0.00 log i/o's/second
----------------------
BUFFER POOL AND MEMORY
----------------------
Total large memory allocated 17582522368
Dictionary memory allocated 1618261
Buffer pool size   1048576
Free buffers       1010227
Database pages     37302
Old database pages 13779
Modified db pages  0
Pending reads      0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 1961, not young 12509
0.00 youngs/s, 0.00 non-youngs/s
Pages read 25245, created 12063, written 2341874
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 37302, unzip_LRU len: 0
I/O sum(0):cur(0), unzip sum(0):cur(0)
----------------------
INDIVIDUAL BUFFER POOL INFO
----------------------
---BUFFER POOL 0
Buffer pool size   131072
Free buffers       126195
Database pages     4738
Old database pages 1766
Modified db pages  0
Pending reads      0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 47, not young 0
0.00 youngs/s, 0.00 non-youngs/s
Pages read 3177, created 1561, written 390400
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 4738, unzip_LRU len: 0
I/O sum(0):cur(0), unzip sum(0):cur(0)
---BUFFER POOL 1
Buffer pool size   131072
Free buffers       126202
Database pages     4747
Old database pages 1732
Modified db pages  0
Pending reads      0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 57, not young 0
0.00 youngs/s, 0.00 non-youngs/s
Pages read 3144, created 1603, written 377393
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 4747, unzip_LRU len: 0
I/O sum(0):cur(0), unzip sum(0):cur(0)
---BUFFER POOL 2
Buffer pool size   131072
Free buffers       126359
Database pages     4584
Old database pages 1682
Modified db pages  0
Pending reads      0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 1596, not young 12509
0.00 youngs/s, 0.00 non-youngs/s
Pages read 3159, created 1431, written 286695
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
No buffer pool page gets since the last printout
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 4584, unzip_LRU len: 0
I/O sum(0):cur(0), unzip sum(0):cur(0)
---BUFFER POOL 3
Buffer pool size   131072
Free buffers       126376
Database pages     4563
Old database pages 1679
Modified db pages  0
Pending reads      0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 23, not young 0
0.00 youngs/s, 0.00 non-youngs/s
Pages read 3060, created 1503, written 217282
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
No buffer pool page gets since the last printout
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 4563, unzip_LRU len: 0
I/O sum(0):cur(0), unzip sum(0):cur(0)
---BUFFER POOL 4
Buffer pool size   131072
Free buffers       126427
Database pages     4515
Old database pages 1683
Modified db pages  0
Pending reads      0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 39, not young 0
0.00 youngs/s, 0.00 non-youngs/s
Pages read 3113, created 1402, written 296757
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 4515, unzip_LRU len: 0
I/O sum(0):cur(0), unzip sum(0):cur(0)
---BUFFER POOL 5
Buffer pool size   131072
Free buffers       126346
Database pages     4604
Old database pages 1681
Modified db pages  0
Pending reads      0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 48, not young 0
0.00 youngs/s, 0.00 non-youngs/s
Pages read 3120, created 1484, written 220370
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 4604, unzip_LRU len: 0
I/O sum(0):cur(0), unzip sum(0):cur(0)
---BUFFER POOL 6
Buffer pool size   131072
Free buffers       126053
Database pages     4883
Old database pages 1815
Modified db pages  0
Pending reads      0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 104, not young 0
0.00 youngs/s, 0.00 non-youngs/s
Pages read 3276, created 1607, written 259821
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 4883, unzip_LRU len: 0
I/O sum(0):cur(0), unzip sum(0):cur(0)
---BUFFER POOL 7
Buffer pool size   131072
Free buffers       126269
Database pages     4668
Old database pages 1741
Modified db pages  0
Pending reads      0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 47, not young 0
0.00 youngs/s, 0.00 non-youngs/s
Pages read 3196, created 1472, written 293156
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 4668, unzip_LRU len: 0
I/O sum(0):cur(0), unzip sum(0):cur(0)
--------------
ROW OPERATIONS
--------------
0 queries inside InnoDB, 0 queries in queue
0 read views open inside InnoDB
Process ID=9652, Main thread ID=00000000000028B4 , state=sleeping
Number of rows inserted 425605, updated 1126794, deleted 24758, read 3734292042
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s
Number of system rows inserted 1841, updated 1056, deleted 1656, read 1362568
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 69.28 reads/s
----------------------------
END OF INNODB MONITOR OUTPUT
============================

MYSQL Tuner Tips
https://i.gyazo.com/107f94f2e69fafe58d6f2125ff3c9ccc.png

I would highly appreciate any input on how we can make the database happier!
If I’m missing any information, let me know happy to provide any extra info!