cPanel site creation very slow

Discussion in 'Apache Migration/Compatibility' started by ffeingol, Aug 14, 2009.

  1. ffeingol

    ffeingol Well-Known Member

    I'm not sure this is a LSWS problem, but I'm attacking it from all sites. We create cpanel accounts via our billing system. It uses the xml-api to create the accounts. The account creation process is very (very, very) slow. If we manually create the account it appears to be the 'restarting services' that's the slow part.

    I seem to remember another thread on this but I can't find it. Any ideas what's causing this slow down?

  2. ffeingol

    ffeingol Well-Known Member

    Any thoughts on this one? This is beginning to become a serious issue. When I set get added/add-on gets created the server load can sometimes spike from a normal 2 - 3 to 20 - 30 for 5 or 10 minutes. This is beginning to cause serious problems.
  3. Tony

    Tony Well-Known Member

    How big is your httpd.conf? cPanel account creation gets pretty slow on Apache as well as the httpd.conf gets larger. As for the load spikes is it possible it's from having extra PHP processes running while lsws is being gracefully restarted. This can use quite a bit of memory depending on how active the server is.
  4. ffeingol

    ffeingol Well-Known Member

    Hello Tony,

    That is not what I want to hear. Define 'big'. Number of lines in httpd.conf, number of hosts? One of the reasons for using LSWS is having more sites on one server. If LSWS dies with bigger httpd.conf's that kind of kills the purpose. Any know work-arounds?
  5. Tony

    Tony Well-Known Member

    100,000 lines?

    The bigger the httpd.conf gets the slower it's going to be at doing the reload. cPanel adds a lot of includes to or used to. You'd have something like this on every vhost:

    Include "/usr/local/apache/conf/userdata/std/2/username/*.conf"

    They may have fixed the logic in adding that now or maybe not my memory on that is a little fuzzy as we changed our templates around. That can really slow down reloads of the httpd.conf.

    My experience is lsws is far better at reloads than Apache is. The more vhosts you get the longer the reloads become on either system. At least with lsws it's graceful system handles it much better than Apache does.

    Your issue does seem very strange though even our most loaded and biggest httpd.conf's can handle them without major issues. The only thing that happens for us is memory goes up as more PHP processes are there to handle the few remaining requests before the reload finishes. I could see it being a problem if you had tons of restarts in a row but you would probably have Apache completly down if that happened.
    Last edited: Aug 17, 2009
  6. ffeingol

    ffeingol Well-Known Member

    Nope, then these are not big :) They are only about about 25K lines. It's just very inconsistent. Sometimes it works fine, no load etc, the next time it spikes. The biggest problem (of course) is that you can't control when it will happen. Clients add add-on/sub-domains at any time.

    cPanel is still putting those include lines in but they are all commented out by default.
  7. mistwang

    mistwang LiteSpeed Staff

    4.x should work better on this.
  8. ffeingol

    ffeingol Well-Known Member


    I'm not sure that we're ready to upgrade to 4.x yet. We need to see a bit more stability in that version.

    What is really throwing us is that it's not consistent. Things will be fine (no long restart, no high load) for a bunch of domain adds then 'poof' one will just tank the server.

Share This Page