Wordpress 3.x + Taxonomies = brakes when editing. Why?

Question

WordPress

Firework! If you have worked with WordPress, you are probably familiar with the fact that taxonomies for posts appeared in wp 3.x. I actively use them. And I still can’t understand why when adding a couple of taxonomies, editing a post turns into flour. The brakes while maintaining the post are simply unrealistic. It seems nothing supernatural pieces 5 records in each of the taxonomies, a few custom fields in the post. For example: a typed post “book” has a couple of fields (let's say the year of publication and circulation) and a couple of taxonomies “authors” and “genres” in which there are 5 positions each. And that's it. every post will be saved for 30 seconds and opened in the same way (I mean for editing). I don’t do any tricks of the ears, everything according to the manual. Checked on several hostings. When showing posts, I did not observe such problems. I have no problems with the speed of the computer / Internet. Has anyone figured out where this problem comes from?

Answer 1

What browser do you use?
I have long noticed terrible brakes when working with the Wordpress admin panel in FireFox. At the same time, everything flies in Chrome.

Answer 2

I have been torturing these chips for a long time and do not observe any brakes.
Put in /admin/post.php to the top

define('SAVEQUERIES', true);
$time_start = microtime(true);

and at the end

$time_end = microtime(true);
echo "<!--";
print "Total time: ".($time_end-$time_start)." sec\n";
print_r($wpdb->queries);
echo "-->";

and after saving you will see all requests to the database and the total time of work,
if indeed the total time will be large (it means the browser and scripts on the client are not to blame), then see which requests to the database are taking a long time (time in seconds, after the request itself). You can also see where they are called from ... in general, then the usual work on optimization :)

Answer 3

If the topic is still relevant, although maybe someone else will need it ...
I had the same problem. Decided it quite by accident.
I updated the PHP version for the site in the hosting provider's control panel, and it all worked!

Answer 4

The problem is something else.