Making nginx "feel" faster?
Phillip B Oldham
phill at theactivitypeople.co.uk
Mon Mar 10 10:52:29 MSK 2008
Yes - lighttpd had lots of problems with 500 errors due to php processes
ending unexpectedly. Haven't tried apache, but I don't much fancy
playing with fastcgi with apache or re-compiling php.
Igor Sysoev wrote:
> On Sat, Mar 08, 2008 at 02:51:56PM +0000, Phillip B Oldham wrote:
>
>
>> Hi guys
>>
>> I'm working on a mediatemple server (US) from the UK and it looks like
>> there's a limit with the bandwidth from the server. Sites on that box
>> are slow, whether they're dynamic or not. nginx has 8 worker threads
>> (with 8 php-fastcgi threads waiting), keepalive is set to 3, static
>> files are being told to cache, and gzip is enabled.
>>
>
> You do not need worker per each php-fastcgi process.
> Single worker is enough for this.
>
>
>> Are there any other tweaks I can do to nginx to make the responses feel
>> faster? Maybe reduce the chunk size or something?
>>
>
> I have no idea. Have do you tried other servers: lighttpd, Apache in this
> environment ?
>
>
>
--
*Phillip B Oldham*
The Activity People
phill at theactivitypeople.co.uk <mailto:phill at theactivitypeople.co.uk>
------------------------------------------------------------------------
*Policies*
This e-mail and its attachments are intended for the above named
recipient(s) only and may be confidential. If they have come to you in
error, please reply to this e-mail and highlight the error. No action
should be taken regarding content, nor must you copy or show them to anyone.
This e-mail has been created in the knowledge that Internet e-mail is
not a 100% secure communications medium, and we have taken steps to
ensure that this e-mail and attachments are free from any virus. We must
advise that in keeping with good computing practice the recipient should
ensure they are completely virus free, and that you understand and
observe the lack of security when e-mailing us.
------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20080310/91520041/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: phill.vcf
Type: text/x-vcard
Size: 261 bytes
Desc: not available
URL: <http://nginx.org/pipermail/nginx/attachments/20080310/91520041/attachment.vcf>
More information about the nginx
mailing list