Large httpd.conf Files

Discussion in 'Apache Migration/Compatibility' started by Crosswinds, Jun 16, 2006.

  1. Crosswinds

    Crosswinds New Member

    I ran into an interesting issue.

    I have a cPanel server with about 500 small domains on it - very low traffic. Currently using Apache+php-fcgi and it's working out pretty well, but I like simplicity.

    I decided to try lsws to see how it works, etc and my results have not been encouraging.

    The httpd.conf files has a total of 1595 virtual hosts - most of which are subdomains and parked domains. Apache has no issue loading this up or running.

    I fired up lsws and the import took a very long time (30-40 mins - I went and got a coffee). Starting up lsws and going to a domain on the system (on the lsws port) I get the lsws welcome screen.

    No problem, I go to the admin port and.... it times out. Every time. admin_php eats all available cpu and I've upped the memory and php execution time and it simply cannot process that many virtual hosts efficiently.

    Any recommendations? (heh and no, moving some onto another server isn't a good recommendation - Apache is doing quite a good task at the moment - I am simply looking for an even better customer experience - they are quite happy as it is). :D
  2. xing

    xing LiteSpeed Staff


    We are currently working on a revamped web admin interface which address this problem. The current web admin code has not been optimized for speed when dealing with several hundred vhosts thus you see the admin_php process chewing up CPU and timing out.

    Please email the apache httpd.conf to so we can verify your problem, create a fix for you to test, and commit it to our internal 2.1.17 release.
  3. mistwang

    mistwang LiteSpeed Staff

    While Xing tuning the web admin interface, you can try let LSWS using httpd.conf directly instead importing httpd.conf into LSWS configuration format. We have user using LSWS with Cpanel successfully, this way, you can still manage vhosts within Cpanel without importing httpd.conf again and again.

    Just install a fresh copy of LSWS and check out the "Apache configuration" under "server"->"general".

Share This Page