After upgrade to 2.7 – very slow

The fresh install has no .htaccess file.

And the tip which I get all the time: “Change your provider”. It’s a little bit to simple. Sorry to say – but I am quite disappointed – I started with my blog in october 2006 and never had such a problem…

What I noticed with my days of using wp 2.7 is that when you first started using it it was really fast but on that process wp 2.7 somehow s0metimes fast and s0metimes really slow.

And I noticed that when you’re experiencing the slow 2.7 just try to clear private data, like the cache esp. the cookies and it’ll be fast again. But it’s very inconvenient though.

I thing wp 2.7 have some issue on cookies, not that sure but that is what I noticed.

My provider says that this is a problem with WordPress – in other forums I have to learn that this is a server problem – super situation:

Server Information

OS Linux
Server Apache/2.0.46 (Red Hat)
PHP v5.1.6
MYSQL v4.1.18
GD bundled (2.0.28 compatible)
Server Hostname https://www.blogkom.net
Server IP:Port 80.74.149.31:80
Server Document Root /home/httpd/vhosts/blogkom.net/httpdocs
Server Load 10:47:53 up 3 days, 17:02, 0 users, load average: 0.86, 0.81, 0.66 0.86
Server Date/Time 15. Dezember 2008 @ 11:47
Database Data Disk Usage 14.1 MiB
Database Index Disk Usage 1.6 MiB
MYSQL Maximum Packet Size 1,024.0 KiB
MYSQL Maximum No. Connection 700
PHP Short Tag On
PHP Safe Mode Off
PHP Magic Quotes GPC On
PHP Memory Limit 64.0 MiB
PHP Max Upload Size 25.0 MiB
PHP Max Post Size 8.0 MiB
PHP Max Script Execute Time 30s

Same thing here,

VERY VERY SLOW after upgrading to 2.7

I upgraded because of the promiss of better performance. Speed dropped to about 1/10th. Terrible.

Cheers, Berend

@berendraap
We are searching for the problem – seems that version 2.7 have special needs for the server – or other way round: the server has a special setup which WordPress can’t handle…

Will report as soon as I have more information.

One thing I seem to have noticed quite often with the slowness issue is that it is often related to those with MySQL 4.x. I wonder if MySQL 5 would be an improvement?

@bernardborealis
Thanks for your input – indeed my provider runs MYSQL v4.1.18 on the server.

sorry but with my etch and mysql 5.0.32-7etch8 I had the same problem, sometimes the page loads in some seconds and next moment 2 minutes…

It’s very strange…
mysql-server-5.0 5.0.32-7etch8
apache2 2.2.3-4+etch6
libapache2-mod-php5 5.2.0-8+etch13
php5 5.2.0-8+etch13

I’m using a windows machine and all previous versions of the wp dashboard have loaded quickly for me. But since upgrading to 2.7 it has slowed down considerably. It can take up to 60 seconds to reload the dashboard. More often it is 40 or sometimes 20 seconds. But it never gets faster than that.
I’ve tried deactivating all the plugins and engaging gears. But neither of these processes has any effect.
The public part of the blog is OK.
If anyone has managed to sort this problem I’d be very grateful.

Did you try the patches here – at least the last one?

Please add me to the growing list of dissatisfied users of 2.7. The first beta I tried was much better. The last before final started this abysmal trend of the dreaded slows.

It sometimes takes FIVE minutes for the Edit page to load. This is unacceptable.

We hope this is fixed soon. It is on the WP side, not the server side.

wl

It sometimes takes FIVE minutes for the Edit page to load. This is unacceptable.

We hope this is fixed soon. It is on the WP side, not the server side.

No, I’m sorry, but just, no.

No page can take five minutes to load and it not be a server issue. Period. Five minutes is ridiculous. So ridiculous, that your server is misconfigured in a way that causes something to block for ridiculous timeout periods. Heck, default PHP installations won’t even RUN for that long, they cut out after 30-60 seconds.

In other words, the only way that you get a multi-minute page load is that something WordPress is trying to do (contact another site, do a DNS lookup, could be anything) is causing your broken server to sit there, waiting for an answer that will never come, over and over again.

“Slowness” is not a specific enough problem for us to solve. Nobody here can likely help you solve it either. And it’s not a problem with WordPress.

You need to find a) somebody who knows servers, b) somebody with access to your specific server, and c) somebody who knows PHP and have them debug this for you. Because something on your server is badly broken, but it could be any damn thing so there’s no way for us to narrow it down. You have to narrow it down. Once you know what the actual problem is, THEN we can judge whether or not we can do something about it. Even then, it would be, at best, a detection and workaround to servers with your specific problem, not a problem in WordPress itself. The problem still would need to be fixed on your server.

But until we know the problem, we can’t even work around it. And if you can’t tell us what the problem is, then we have no way to magically guess WTF is wrong with your box.

That’s just how it is. Sorry.

If this is unacceptable to you, then I suggest that you switch off WordPress to something else. Not that it will help you any, really, but hey, worth a try.

Wow. You represent WordPress? That is terrible marketing sir!

I have been a loyal WordPress user for years and have had no problems until this issue in 2.7 that results in incredibly slow page loads. Something in the code is changed that causes this. Our server was not changed and worked perfectly fine with the most recent release before 2.7. We are running the most recent version of php and mysql, FYI.

I hope that a solution is found quickly. Suggesting that users “switch” is just very sad and quite surprising.

@otto42
Sorry, that’s the old “game” – my provider tells me that there must be something wrong with WordPress – you are telling us that it must be something wrong with the server – period – other word: a blocked situation.

To switch the server or to switch the program is not a solution in my opinion. My goal: To find and solve the problem. But I don’t have (root) access to the server and I have only little skill in PHP.

Yes I know, to find a problem one must have a lot of information, as much as possible. But it is not so easy to give such information – to test software and find bugs in not all users daily business.

On the other side: If you have a lot of feedback about “slowness” of version 2.7 there “must be something”…

[BTW. Sorry, English is not my native language.]

Wow. You represent WordPress? That is terrible marketing sir!

1. No, I represent myself.
2. WordPress is free, open source software. Use it or don’t use it. It makes no real difference to us.

Something in the code is changed that causes this. Our server was not changed and worked perfectly fine with the most recent release before 2.7.

See, a lot of people get this fundamentally wrong. You’re basically saying “X is the only thing that changed, so the problem must be in X!” The problem is that that is simply not true. The changes in X might have cause the problem in Y to get triggered now, where they were not being triggered before. This is likely because X has lots of new functionality and changes. But the problem is still in Y, X cannot fix it and retain the new functionality.

Get it? Just because it worked before WordPress 2.7 does not mean that the problem is in WordPress 2.7. WordPress now does a lot of new things that it didn’t do before, and clearly, one of those new things doesn’t work on your server. But the server is still where the problem is.

Suggesting that users “switch” is just very sad and quite surprising.

I’m always amazed at people thinking that we’re under some obligation to help them above and beyond the call of duty or something, or that we’re trying to push a product or anything else.

Let’s be perfectly clear here:
-You did not pay for WordPress.
-You are not paying anybody here for support.
-The people here that help people are volunteers, who help people out of the kindness of their hearts.
-And if you’re not willing to diagnose your problems and get helped by those people, and instead just want to complain endlessly about how upset you are, then your problem is completely unsolvable. And in that case yes, I very well will tell you to take it elsewhere and stop using the program that you did not pay one thin dime for. Why? Because we’re here to help people, and if the only way I can help you is to say “Stop using WordPress, it’s not for you”, then that is exactly what I will do.

This should not be construed as insulting, and I’m not trying to be rude. I’m just stating the way it is. If you are going to refuse all the help that we can give you and reject the only possible ways that we can help you, then I’m left with no alternatives but to try help you in the only way left, which is to tell you to go to some other package that works for you.