Admin pages WAAAAAYYYYY SSSLLLLLOOOOOWWWWW

  • We’re using WordPress in a College, the idea being that students get a wordpress blog for their classes and also as a portfolio after graduation. So we installed WordPress 3.0 with iPower as a hosting service, enabled multi-user, and ran with it.

    Sadly, if there are more than about 3 students (or any other people) editing their blogs at the same time (for example, if the professor is showing 30 students how to use it in a computer lab) the response time is so slow it’s unacceptable. Like, 5 minutes to save a post. Or open a post for editing. Or creating a new post.

    We’ve upgraded to 3.0.3, deactivated all our plugins (about a dozen), run update.php, tried to optimize our PHP configuration, etc. The CPU time is being taken up by Apache, not MySQL. If 5 users are trying to use the system, 5 instances of Apache will be taking up 3-5% of CPU time each. We started this in August, and have about 35 blogs, with perhaps 1 or 2 entries each, so I doubt it’s a MySQL problem.

    We’re running Debian Linux version 7, a virtual server, with PHP 5.2 and MySQL 5.0.32.

    Any additional thoughts on what are our obvious next steps to try to fix the problem before next semester starts?

    TIA!

    Cheers!

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

  • How much RAM?

    Is this on your own box in-house or did you buy hosting somewhere?

    Thread Starter Carl Thelen

    (@cthelen)

    it’s got 2.00 GB RAM, hosted with a company called iPower. The Plesk control panel says,

    “CPU GenuineIntel, Intel(R) Xeon(R)CPU E5410 @ 2.33GHz
    Version psa v8.6.0_build86081001.10 os_Debian 4.0
    OS Linux 2.6.18-028stab057.4″

    among other things.

    Another potentially useful bit: I turned on debugging for a little while, and got tons of “deprecated” errors. For example, “Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in <filepath>functions.php on line 3237” All of the errors point to functions.php. We initially installed 3.0.1 in August (I think) and recently upgraded to 3.0.3. Do these errors imply that we’ve got out-dated plugins? Or is it possible these errors come from WP core?

    Would it be useful to disable all plugins, and turn on debugging again, and see if the errors continue to come up?

    Cheers!

    P. S., many thanks to Andrea_r for answering so many questions!

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Would it be useful to disable all plugins, and turn on debugging again, and see if the errors continue to come up?

    And theme to Twenty Ten as well, but yeah.

    Have you any caching plugins set up on WordPress? Any for the server itself?

    what ipstenu said. ?? She’s smart too.

    Thread Starter Carl Thelen

    (@cthelen)

    OK, I did all of the above. The errors are gone (yay!), and an initial test seems to indicate that the response time is better too. We’ll do another test tomorrow and see….

    Thanks for all your help so far!

    My magic hat says it was a plugin.

    Check your error logs too. those things are handy. ??

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Admin pages WAAAAAYYYYY SSSLLLLLOOOOOWWWWW’ is closed to new replies.