I would recommend using the uWSGI approach. It has some very nice features.
'Theoretically', socket should avoid some networking stack overhead. In practice I haven't taken benchmarks, but from experience tcp/ip is more stable (this is the case for PHP, but I'm pretty sure it is related to bugs in the php-cgi code). Besides that, take care of the usual: keep alive connections, IO/cache enabled for static contents, maybe throw in some load balancing into the equation ... Maybe someone with more experience deploying Django apps could give some more tips. kevin beckford wrote: > > Lately I've been wondering about some of the wizard options with > Django. Specifically, do I need to adjust things to have a high > performance setup? > > Is it better to use a tcp/ip connection or a socket? > -- [email protected] http://unixwars.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
