post WPMU->WP3 upgrade slowness – transient_feed?

  • Since the upgrade from WPMU 2.9.2 to WP 3.0.1, we’ve had problems with slowness. There was a big improvement after I ran a repair and optimize on all the MySQL tables, but we still notice that certain blogs run more slowly than others.

    I noticed that for the blogs running more slowly, the wp_x_options table is especially large in size – e.g. several hundred KB in size rather than < 100 KB in size. And the large entries in the table are generally named “_transient_feed_[some long hex]”.

    It’s hard for me to tell what these are for – I think they’re for caching something, but the blogs with these do not have RSS feeds in their widgets or anything like that. Google searches about these are mostly turning up “oh noes I am haxx0red” posts, but I don’t think that’s the issue here.

    If I delete these caches and run an optimize on the options table, the blog will temporarily speed up again. So clearly they’re evil! No, I suppose not. But can anyone explain to me what the transient_feed entries are for, and whether they might be causing this issue, and if so, how I can tame them? Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)

  • They are cached feeds from the dashboard feeds – yes you can delete at will.

    Thread Starter nadaoneal

    (@nadaoneal)

    Thanks Andrea. I read this article:
    https://codex.www.ads-software.com/Dashboard_Widgets_API#Advanced:_Removing_Dashboard_Widgets

    to see how to suppress the dashboard widgets that have these feeds. I’m currently testing to see if this fixes the slowness issue. I will post again if I find out anything useful for posterity.

    Thread Starter nadaoneal

    (@nadaoneal)

    So, I tried the fix – suppressing the RSS feeds on the dashboard, deleting the transient feed records out of the options tables, and then running mysqlcheck -Aaeo from the command line. This has made a significant improvement, but we still notice (less severe) slowness from time to time, especially on the backends of blogs that were upgrade from WPMU.

    Including the simple perl script that I used to delete the transient_feed records from the options tables, in case it saves someone 10 minutes in the future…

    #!/usr/bin/perl 

use DBI;
use strict;

my $db_name='****';
my $db_host='****:***';
my $db_user='***';
my $user_pass='****';
my $dbh = DBI->connect("DBI:mysql:$db_name:$db_host",$db_user,$user_pass); 

# first, get all the "options" tables
my (@options_tables);
my $query = "show tables;";
my $sth = $dbh->prepare($query);
my $rows = $sth->execute;
while (my @data = $sth->fetchrow_array()) {
	my $tbl_name = $data[0];
	# options table?
	if ($tbl_name =~ /wp_[0-9]+_options/ ) {
		push(@options_tables,$tbl_name);
	}
}
$sth->finish; 

# delete the transient feed junk from the options tables
foreach my $opt_table (@options_tables) {
	print qq~deleting from $opt_table...\n~;
	$query = qq~delete from $opt_table where option_name like "%transient_feed%";~;
	$sth = $dbh->prepare($query);
	$rows = $sth->execute;
	$sth->finish;
}
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘post WPMU->WP3 upgrade slowness – transient_feed?’ is closed to new replies.