Typical settings for these environments

Discussion in 'Install/Configuration' started by joek168, Apr 26, 2010.

  1. joek168

    joek168 Member


    Are there recommended configuration settings for various sized machines?

    e.g. for a 2GB RAM machine start with these typical settings, for a 8GB or 16GB machine start with these settings, etc.

    My litespeed server is on a VPS and I'm expecting a traffic spike. I plan to size up my machine for this spike. I'd like to know if there are recommended settings for 2GB of RAM, 8GB, and 16GB.


  2. NiteWave

    NiteWave Administrator

    there may not exist.

    when at your traffic spike, run "top" alike tools, try to identify the bottle-neck of your site. Often we heard of app/site is CPU-bound, IO-bound, network-bound or memory-bound(however, there seems to be less chance to hear about memory-bound). sometimes, double memory has no much difference regarding overall performance.
  3. joek168

    joek168 Member

    Was hoping to be more proactive

    I've been running httperf to try to get a handle on how things will respond. Is there not some guidelines for configuration settings for various sized machines?

    What do I look at results from httperf or other benchmarking software, how do you know where to start tweaking?
  4. joek168

    joek168 Member

    Some additional insight

    I ran some more test runs of httperf and this time I did some runs that included mysql db querys and some runs that did not.

    Litespeed handled the non-mysql connections with no problems. I went from 200 conns/sec to 400 conn/sec and no client timeouts.

    Then when adding the runs with mysql querys was where I would have problems.

    I'm using PHP5 and MySQL 5.0.77. Are there specific Litespeed configuration settings that can be tweaked to maximize the use of PHP and MySQL?
  5. NiteWave

    NiteWave Administrator

    regarding benchmark, please refer our blog. We have run some benchmarks a few months ago, and the result were good and encouraging.

    litespeed don't connect to MySQL directly, PHP make connections with MySQL. For large volume traffic, MySQL used to be bottle-neck. I experienced an example of poor performance of PHP + MySQL recently. The server's hardware configuration is good, MySQL itself is responsing fast. However, the PHP DAL(database access layer) is not efficient at all and made some page very slow to load(for example, 45 seconds).

Share This Page