WP Transients must be used responsibly
Sunday, January 28, 2018
We ran into an interesting issue with WooCommerce at work. First, here is the subject of the support request we got from our hosting provider: The site is generating ~150MB/sec of transaction logs, filling 500GB of diskspace Holy. Shit. A WordPress site should not be generating that much data. 150MB per second? Wow. How? Why? The simple explanation is that there is a bottleneck in WooCommerce with the filtered layer nav query objects using single transient record.