Good evening, have little problem with Nginx configuration. I'm using it for script who streaming data to user from another server, so it's like proxy. But this action requires lot of CPU time. I have almost default Nginx configuration, it works with fast-cgi, i wonder maybe some one know something about tweaking Nginx for streaming/proxy?
Asking for advice about Nginx
- Thread starter kiladila
- Start date
- Status
40 comments
The issue is not necesrilly nginx, but the php interpriter you're using. When you say its running a 'script' I assume you mean via php.
I run a site that recieves over 150,000 UV/day. It runs nginx + php-fpm (the interpriter) and then apc to cache opcode.
I'd suggest you try fpm before switching back to the almighty resouse hog known as apache.
I run a site that recieves over 150,000 UV/day. It runs nginx + php-fpm (the interpriter) and then apc to cache opcode.
I'd suggest you try fpm before switching back to the almighty resouse hog known as apache.
Nginx will fail really hard with dynamic load. It's designed to handle load from static files.
You're streaming data which effectively means there's script interaction at some point. That's where nginx tends to fail, hard. And I say that from experience. I used to run a public leech server too. And nginx failed in a few hours. I switched back to optimized Apache, and I was good to go!
You're streaming data which effectively means there's script interaction at some point. That's where nginx tends to fail, hard. And I say that from experience. I used to run a public leech server too. And nginx failed in a few hours. I switched back to optimized Apache, and I was good to go!
As I explained before, its not nginx thats the problem, its what your using to interpret php FOR nginx. An optimized apache setup will probably work, but if you're actually serving content from the server, then I'd stick with nginx. As I said before, why not give php-fpm a go?
On the other hand, you could have the best of both worlds. Use nginx to serve static content and have it proxy to apache for anything dynamic.
Just my two cents.
On the other hand, you could have the best of both worlds. Use nginx to serve static content and have it proxy to apache for anything dynamic.
Just my two cents.
Please tell if streaming data is DINAMIC or STATIC content? If we using simple rapidleech with schema: FILE HOST >> SERVER >> USER i think that we serving static content (only files), but in my situation i'm streaming files directly via proxy script, so this is dynamic content then?
Show me one benchmark where mpm prefork beats apache under a decent load (atleast 10 req/s, although im sure it would beat it under that) and I will eat my hat.
Streaming static files definately used nginx, if you are serving large files try directio, else ensure sendfile is on.
If files are never read twice then compiling nginx with aio (asyncronous IO) will give a performance increase howeaver if not dont worry (AIO skips file caching)
- Status