I found it a bit odd that writes for linux went down from 22MB/s to 17MB/s when Windows writes went way up from 13MB/s to 34MB/s. This at the same time as read performance went up to 27MB/s for both systems.<p>Edit: Seems like it's a regression that will likely be fixed for 0.6.1.
Am I the only one that thinks that Windows support was not really worth the time? Sure, you get to support a huge chunk of the OS market, but what are the real implications of Node running natively on Windows?
"Native Windows support using I/O Completion Ports for sockets."<p>"Integrated load balancing over multiple processes."<p>These two improvements are just the nudge I needed to start tinkering with Node. I've been following along and reading about node almost daily but native windows support and integrated focus on multiple processes make a big difference to me. I can no longer sit on the sidelines.<p>Thanks for picking me up and shoving me onto the field!
Direct link to a list of changes you have to make to your codebases: <a href="https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6" rel="nofollow">https://github.com/joyent/node/wiki/API-changes-between-v0.4...</a><p>Question: Since this doesn't look that complex, is anyone working on an automagical translator from 0.4 to 0.6 that people could use?
Next for windows developers is trying to get npm to work. The sheer popularity of unix tooling in the build process means that using node libraries is likely to remain a challenge.
uhm, according to their benchmark io.js write performance dropped from 21mb/s to 17mb/s in linux but rose from 12mb/s to 33mb/s in windows.
So it seems that windows node implementation is now twice faster (for I/O) than linux one..are they only focusing on windows platform?
Node Cluster? <a href="http://nodejs.org/docs/latest/api/cluster.html" rel="nofollow">http://nodejs.org/docs/latest/api/cluster.html</a><p>Is it me or does this look like the early makings of an erlangish otp, eh?