> > Łukasz, > > Great work! How does that compare to (in order get an idea of baseline): > > 1. Serving the same file by nginx only? > 2. Let nginx balance between nodes (nginx->nodes)? > >
The whole purpose of routers (http,https,spdy...) is to have the fastest possibile way to route a request to backend with the minimal amount of logic. This is a common need for ISPs and PaaS, where you want the customer instance to be used instead of the shared one. (For example, the customer buys resources for serving its static files and their apps, and you want hardware resources used by him to accounted to him TOTALLY. If you serve all of the static files from a single instance you are again weak to a single user eating all of the resources). This is the common (even if probably not the only) scenario for which the new features of uWSGI (like offloading) are meant. So, very probably, if you make a benchmark in proxying between uWSGI and nginx you may be surprised by uWSGI performances, but that is because it is extremely simpler. Regarding static files nginx has a lot of internal optimizations that only recently we have started adding to uWSGI (like using the shared cache for storing path resolution results). So if you are not in the hosting market, your best bet is still nginx on front for serving static files and proxying. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
