Project

General

Profile

[Solved] performance problem

Added by badpenguin over 7 years ago

I've noticed a performance problem serving a static website.
Only 8 parallel download are started.
It seems php-fpm popping up in the "top" process list for static content too.
How can i fix this?


Replies (4)

RE: performance problem - Added by gstrauss over 7 years ago

Multiple solutions. Your favorite search engine is your friend.

You probably want to configure lighttpd to serve static content instead of PHP.

If your machine is powerful enough, you might configure php-fpm to handle more connections in parallel instead of being limited to 8.

RE: performance problem - Added by badpenguin over 7 years ago

well the problem is not PHP; i host multiple domains but this one has only static content.
I'm starting to think that its the some chormium browser that is limiting to 8 the maximum parallel downloads ?

However when using "google hosting" services via HTTPS they have SPDY and chromium seems to download more files in parallel (almost all!).

I started to compare speed of my VPS with lighttpd against this google service... but maybe i'm comparing apples vs bananas.

I wanna also make clear that i've no PHP problem with wheezy+xcache... performance are very good about PHP scripts!

RE: performance problem - Added by gstrauss over 7 years ago

Only 8 parallel download are started.

You might be talking about a single browser.

The number of downloads in parallel is less important than total throughput.

lighttpd does not support SPDY or HTTP/2, though that may happen in the more distant future, so the number of parallel downloads for a single client will be the number of connections the client makes to the server.

Seeing php-fpm in 'top' is likely unrelated if you have configured lighttpd to serve the static content.

RE: performance problem - Added by badpenguin over 7 years ago

Aye definitively seems a browser thing
i was incorrectly comparing HTTP+lighttpd with HTTPS+google+SPDY.

Using server status i figure it out that the PHP was a request for another domain that has PHP,
so just ignore it.

Sorry!

    (1-4/4)