Sorry for the delay in seeing the post; there was a mailing list problem. On Tue, 2006-08-29 at 09:15 -0700, Juergen Weber wrote: > In the Slashdot article "The trouble with the Nagle > algorithm" > (http://developers.slashdot.org/comments.pl?sid=174457&threshold=1&commentsort=0&mode=thread&cid=14515105) > by John Nagle himself, it is recommended against > performance losses: "The user-level solution is to > avoid write-write-read sequences on sockets." > > Unfortunately libneon does exactly this by writing out > first the http header and then the data: > > Of course, you can use TCP_NODELAY. But wouldn't it be > better in the first place to not write the header and > data separately?
Yeah, that would result in less packets on the wire in a few cases; but in general I doubt the performance difference would be noticable. > When first using neon, I spent some time wondering why > a neon http call took 300 ms until I figured out to > set TCP_NODELAY (which got the time down to 10 ms). neon has been setting TCP_NODELAY automatically since 0.24.1 - were you using an older release than that? Regards, joe _______________________________________________ neon mailing list [email protected] http://mailman.webdav.org/mailman/listinfo/neon
