I have been doing some cleaning up in the database of one of my WordPress installs, and I noticed that the wp_options table was about 2.1mb, and had 1200 rows. I've gotten it down to around 800 rows, and 1.2mb. However, there are a bunch of transients.

Should I remove these? I know they don't autoload, so it probably isn't causing strain on the database.

Most of the transients have formatting like the following:


So, is it worth taking the time to remove these?

Thanks for reading! Any thoughts are appreciated.

1 Answer 1


This is not an amount that is likely to cause performance issues. However if you are concerned about leftover transients it is worth looking into if any code you are using is consistently "leaking" them (creating transients that are never removed).

See Are transients garbage collected? for relevant discussion and some code snippets.

  • Thanks for the reply! That thread looks extremely informative as well. Is there any harm in removing the transients?
    – Ryan
    May 4, 2012 at 18:33
  • 2
    @Ryan in plain removing them - no, although there might be no effect either because as Otto notes in his answer on that question you need to run optimize to actually get table reshuffled after removal. As per my answer - it's more important to pro-actively not have them spawned in large quantities than remove them reactively.
    – Rarst
    May 4, 2012 at 18:37
  • Thanks again! I will see if I can find what's causing these, but there isn't an overwhelming amount. I read other people having 100,000's of transients in the wp_options, and while that seems like a more serious problem, having a couple hundred rows of transients doesn't seem like anything to overanalyze... Which is exactly what I'm doing, haha.
    – Ryan
    May 4, 2012 at 18:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.