Delete Expired Transients wordpress plugin resources analysis

Download This Plugin
Download Elegant Themes
Name	Delete Expired Transients
Version	2.0.3
Author	WebAware
Rating	100
Last updated	2015-02-27 11:37:00
Downloads	8633
Download Plugins Speed Test plugin for Wordpress

Home page

Delta: 0%

Post page

Delta: 0%

Delete Expired Transients plugin has no negative impact on PageSpeed score.

Home page PageSpeed score has been degraded by 0%, while Post page PageSpeed score has been degraded by 0%

Delete Expired Transients plugin added 7 bytes of resources to the Home page and 7 bytes of resources to the sample Post page.

Delete Expired Transients plugin added 0 new host(s) to the Home page and 0 new host(s) to the sample Post page.

Great! Delete Expired Transients plugin ads no tables to your Wordpress blog database.

Resources Added (Post page)

Description

Delete old, expired transients from the WordPress options table (wp_options), to prevent them from bloating your database and even slowing down your website.

Unless you are using an object cache (like memcached), WordPress stores transient records in the options table. Many transients are given an expiration time, so in theory they should disappear after some time. In practise, because old transients are only deleted when requested again after they've expired, many transients stay in the database. After a while, there can be thousands or even millions of expired transients needlessly taking up space in your options table, depending on what your plugins are doing.

Delete Expired Transients schedules a daily task to delete any expired transients from the options table. It performs this operation with a single SQL query, and then runs a second query to find any orphaned expiration records and deletes them too.

There are a few other plugins around that clean up expired transients. This one is written for fast performance, set-and-forget scheduled housekeeping, and maximum compatibility. It uses the PHP time to determine whether transients are expired, not the database time (which can be different). It does only one job, and it does it well with the minimum of resources.

Now optimised for WordPress Multisite.