Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using nginx on an embedded platform (OpenWRT) as a reverse proxy in front of an IP camera, and I'm having an issue where the camera is pushing data to nginx more quickly than nginx is able to off-load it to the next stage.

With the reverse proxy removed, extra frames just get dropped and that's that. But nginx seems to buffer a substantial amount of the camera data (as much as 10-15 seconds worth of it), which manifests itself as excruciating lag to the viewer.

So, firstly, are there obvious things that could be done to increase the throughput of the reverse proxy? I'm not using html parsing or translation, just filtering a few directories to other places, and proxying the rest to the camera. Do some of the other proxy features like packet inspection need to be explicitly disabled?

Secondly, how can I drastically reduce or eliminate nginx's willingness to accumulate this large buffer? I would prefer to see it drop packets when overloaded rather than storing them up.


share|improve this question
up vote 2 down vote accepted

You can turn buffering off entirely with However, I don't think you can make it drop data.

share|improve this answer
Awesome, that seemed to do it. Thanks! – mikepurvis Apr 28 '11 at 15:42

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.