Dnia wtorek, 29 listopada 2011 13:26:55 Roberto De Ioris pisze: > As a side note, specifying multiple fastrouter option will lead to only > bind to multiple address. It will not spawn a new process as the old > fastrouter. You can remove it. After 1.0 i will add multithreading support > (no need to have another process) to the fastrouter to gain advantage in > SMP environments.
If I remember correctly from previous tests fastrouter is fast enough to handle few thousands of concurrent requests on single core, and one would need whole lot of hardware for python/ruby backends to clog it. But it may be just good enough to also server static content using --check-static option (at least with varnish in front of it) and in such situation number of requests may spike up to high values from time to time (updating app, new css/js to fetch ...), so it's good to be able to scale it to using more cores. Using vassal for static content is much easier when one is aiming for dynamic infrastructure where worker may be bounced around, the kind of infrastructure that uWSGI make possible in quite simple manner. This is unique feature that IMHO makes all other WSGI solution obsolete. Łukasz Mierzwa _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
