El mar, 25-05-2010 a las 11:31 -0700, kevin beckford escribió: > > A simple change from unix-sockets to a tcp-based php interpreter fixed > > the cherokee-worker cpu problem. > > > > This, of course, is just a workaround, but until it's fixed, just > > switch to TCP for your php interpreter. > > > Why is cherokee using unix-sockets at all? What's the advantage? I > remember asking a while ago about django and Alvaro telling me that > TCP sockets are more robust... ?
I guess it depends. From my experience in OpenBSD with MySQL, using TCP even for localhost it's a performance killer (yes, socket unix it's the way to go). Perhaps Cherokee is better with TCP than with unix sockets, but seems that unix socket can be faster (it doesn't have the extra overhead of the TCP protocol handshakes, checking connection, etc). Just speculating here :) Regards, Juanjo -- jjm's home: http://www.usebox.net/jjm/ blackshell: http://blackshell.usebox.net/ ramble on: http://rambleon.usebox.net/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
