It depends on how many links to objects are in a view and browser configuration. You must count all css, js and img at least. The browser has an upper configurable limit to parallel connections after reaching that limit it starts queuing connections. One thing that comes also into play is http keepalive configuration. If keepalive is active some http request are serialized on a single connection so less connections are needed.
A problem with nginx stable is that it does not support keepalives with backends so the browser cannot reuse the connection for more than a request. Either use a version of nginx that supports keepalives with uwsgi or get the patches and recombile nginx. cherokee should support keepalive. mic Il 25 aprile 2012 00:31, Bruce Wade <bruce.w...@gmail.com> ha scritto: > Curious what is the common connections that a web server should have per > user? Using netstat -an | grep :80 | sort I noticed that one user could have > around 10 connections for some reason. Maybe this is caused by my lack of > nginx + uwsgi knowledge but that seems very high per viewer. > > -- > -- > Regards, > Bruce Wade > http://ca.linkedin.com/in/brucelwade > http://www.wadecybertech.com > http://www.fittraineronline.com - Fitness Personal Trainers Online > http://www.warplydesigned.com >
