Thread

For over a year, this site has been running fine on EE2.  Literally overnight, the CP is now lagging terribly.  Every page takes 21.5 seconds to execute, as compared to the 0.3 seconds yesterday (and for the past year).

Is there something going on that I don’t know about on EE’s end?  Is there some issue with the news feed / update feed?

The front-end of my website loads perfectly fine, it’s only the control panel.

Further, the CSS is slightly screwed up, as the entire control panel appears to have about a 40 pixel body margin around the entire page.

I’m getting this as well. Exact same problems.

I’ve turned off New Version Auto Check, and the problem doesn’t seem to be affect the actual site. However, my client needs to update the site and is having to ages to update anything. Today was the launch date, so the timing could not have been worse.

Any ideas on what’s causing this?

I turned off new version auto check, but it makes no difference.  Still 20+ seconds per page load.  It’s basically completely unusable and has brought production to a halt.

OK, I’ve just verified this is affecting more than 25 of my clients at various hosts.  There is clearly something very wrong on EE’s end.  Can we get a response please?

Well, for anyone else having this problem, this is my temporary fix.  After digging for literally almost 3 hours trying to figure out where exactly the problem was, I isolated it to the version check of EE.

Apparently they thought it was a good idea to use fsockopen to try to find the current version of EE on every single CP page load.  Anyway:

1) Open <system_path>/expressionengine/accessories/acc.expressionengine_info.php

2) Comment out line #161 and add “$fp = 1;” on line #162:

//$fp = @fsockopen($ssl.$host, $port, $error_num, $error_str, 4); 
$fp = 1;

Now my pages load in 0.3 seconds instead of 25.

That worked a treat. Nice work, thank you!

That worked a treat. Nice work, thank you!

You’re very welcome.  Honestly, this is the fastest the control panel has ever been in a year.  I can’t believe how much that one stupid line (even when it works properly) slows things down.

Hey all,

Thanks for the help you provided each other on this. You’re right, it was something on our end. Please check this reply I posted on another support thread that brought up the same issues.