How a bandwidth shortage would manifest itself.

Discussion in 'Install/Configuration' started by NateLloyd, Feb 17, 2006.

  1. NateLloyd

    NateLloyd New Member

    We recently tried an installation of LiteSpeed to see if we would have the same issue with it as with Apache. We ran into similar problems, and started looking at possible external issues.

    Do you know how LiteSpeed would react in a situation where you have a beefy server, lots of requests, and an ity bity pipe to the Internet?
  2. Xorlev

    Xorlev Well-Known Member

    Well, requests would begin to build up, as that small pipe would have to keep connections open longer. With some outbound bandwidth limiting you might be able to optimize that however.
  3. NateLloyd

    NateLloyd New Member

    And that 'building up' of requests...

    Would that result in a growing number of processes, dropped requests, skyrocketing server load, and LiteSpeed automatically restarting every 10 minutes or so? :oops:
  4. Xorlev

    Xorlev Well-Known Member

    It could, yes. Especially if many requests were in process at once. More TCP/IP connections, more processes used (especially if using PHP), and I'm not sure about LSWS rebooting, perhaps when it hits an upper limit and keeps going it kills its self? Will have to let one of the admins or someone more knowledgeable than me answer that.
  5. xing

    xing LiteSpeed Staff

    LiteSpeed should not restart itself due to queued up slow connections. Post some log entries of the restarts. Check error.log and stderr.log.

    If connections are queued in a big way, more cpu resources will be used however I still do not cannot see case where a "slowed" down server due to small pipe causes huge spikes in cpu and load.

    A slow repsonse from the server, for whatever reason, can create a cascading effect where the end user starts refresh their clients thinking you website went down or something is wrong, causing DoS like effect where 500 accessing clients appears like 2500 clients. I imagine this to the case on your end.

    Do you have logs of the litespeed restarting?

    It could be a case you have some logic flaw in your php backend. If all php backend process, fastcgi/lsapi, are unresponses, they are restarted but a slow output to a client should not delay php as php sends all output to the lsws buffered. Once the php sends all the stuff to lsws, the php process's job is done. It is up to lsws to slowly feed the data to the client over the small pipe.

Share This Page