@indexzero @nodejs I tend to lose it, but yes, agreed ;)
-
-
Replying to @mattpodwysocki
@mattpodwysocki@indexzero@nodejs Why is this off-base exactly? Do you dislike the approach, the premise or results?1 reply 0 retweets 0 likes -
Replying to @darachennis
@darachennis@indexzero Same old "multi-threaded is better for CPU-bound, evented better for IO-bound" story.1 reply 0 retweets 0 likes -
Replying to @izs
@darachennis@indexzero The post claims to be interested in showing "app perf", but then does a repetitive CPU-bound op like no app ever.2 replies 0 retweets 0 likes -
Replying to @izs
@izs@darachennis@indexzero What part of the "Hello World" (second bench) has CPU-bound?1 reply 0 retweets 0 likes -
Replying to @obastemur
@obastemur@darachennis@indexzero Think about it. You're just dumping a big string on the HTTP parser. It's a CPU task.2 replies 0 retweets 0 likes -
Replying to @izs
@izs@darachennis@indexzero so, simply expecting node.js to send a Hello World can not be benchmarked ?1 reply 0 retweets 0 likes -
Replying to @obastemur
@obastemur@darachennis@indexzero I'm not saying "can't be benchmarked". I'm saying, no one should be surprised when hotspot is faster.3 replies 0 retweets 0 likes -
Replying to @izs
@obastemur@darachennis@indexzero If your app has to say "Hello" as many times as possible per second, then yes, by all means, use the JVM.1 reply 2 retweets 2 likes -
Replying to @izs
@izs@darachennis@indexzero i prefer nodejx it is faster than jvm ;)1 reply 0 retweets 0 likes
@obastemur @izs @indexzero You may want to check out the GC logs before jumping to conclusions...
-
-
Replying to @darachennis
@darachennis@izs@indexzero thanks for the first technical concern makes sense!. GC is also my concern and preparing a scenario for it.0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.