For the record, I have tested this with Go 1.1 and Node.JS v0.10.20; Go is 22% faster - which means Go can handle 22% more concurrent connections.
On Saturday, July 13, 2013 7:29:03 AM UTC+4:30, Kaveh Shahbazian wrote: > > That was not my intention! > > See; when we have a echo server that echos a little string like "string" > and we set a little buffer in Go, it acts a bit better. > > But in all other cases (bigger messages) Node.JS acts a bit better. > > By "a bit" I mean ~2.5 %. > > And in Node.JS you do not need to worry about buffer size and such things > at TCP level. > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
