> We were running it in "callbacks" mode before and we switched to "fibers-fast" mode recently. It made a big difference: the application is now 5 times faster and it uses 2 or 3 times less memory!!
Niiiiiice. I had a strong feeling that would be the case. Sometimes powerful tools have to be dangerous as well. On Sat, Aug 10, 2013 at 7:26 AM, Bruno Jouhier <bjouh...@gmail.com> wrote: > Good job Gorgi. > > You have tested a single function making several async calls. It would be > interesting to also test with several layers of async calls (async f1 > calling async f2 calling async f3 ...). My guess is that you will see a > significant difference in the way fibers compares with the other solutions > (also it would be interesting to include Marcel's futures library in the > bench) > > We have recently started to benchmark our application. Our app is now > about 100 klocs and it is all written in streamline.js. We were running it > in "callbacks" mode before and we switched to "fibers-fast" mode recently. > It made a big difference: the application is now 5 times faster and it uses > 2 or 3 times less memory!! > > Why is that? This is because we have a lot more streamline-to-streamline > calls than streamline-to-nativeio calls in our app. In fibers-fast mode, > the streamline-to-streamline callls are *not* transformed at all: there are > no wrappers around async function definitions and there are no callback > closures allocated for these calls: an async function calling another async > function is just as lean and efficient as a sync function calling another > sync function. You only get the overhead of closures and fibers at the > boundaries: when node is calling our code (a fiber gets allocated) and when > our code calls node libraries (yield + allocation of a closure). My guess > is that most of the speedup comes from the fact that we got rid of all the > intermediate wrappers and callback closures: a lot less memory allocation > => a lot less time spent in the GC. All this thanks to deep continuations. > > We haven't stress tested the real app in generators mode yet because we > deploy it on 0.10.x but I did a quick bench of the multi-layer call > scenario to compare callbacks, fibers and generators a while ago ( > https://gist.github.com/bjouhier/5554200). Note that this bench was run > with the very first brew of generators (V8 3.19); generators are probably > faster now and will probably get faster in the future (is Crankshaft > enabled today??). So these early results should be taken with a pinch of > salt. > > I'm not saying that fibers will outperform in all scenarios but there are > application scenarios where they shine. > > Bruno > > > 7:11:22 PM UTC+2, spion wrote: >> >> I just finished writing an analysis of many node async patterns (with >> special attention given to generator patterns): >> >> http://spion.github.io/posts/**analysis-generators-and-other-** >> async-patterns-node.html<http://spion.github.io/posts/analysis-generators-and-other-async-patterns-node.html> >> >> There are comparisons for code complexity, performance, memory usage and >> debuggability. >> >> Hope you find it useful and informative. >> > -- > -- > 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 nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > 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 nodejs+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com 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 nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
