We're still in the beginning stages for our next project. What we know at the moment is that we'll definitely have a certain C++ library written by us, and it will be used very frequently. Regardless of which web framework we use, we'll be highly dependent on that library. I was only wondering if Node's Addon module allows us to eke out better performance by reducing the overhead of communication between the web app and the native library. For example, since the bound library would then be in V8's scope, will this eliminate or reduce context switches by the processor, thus potentially offering an increased throughput?
On Monday, 18 March 2013 14:58:19 UTC+5:30, greelgorke wrote: > > there are many modules, which are binding to a c/c++ lib, it's not > primarily for node core extensions. > > the other question, you have to elaborate it yourself. is performance an > issue? what the bottleneck? would a binding solve that issue? What about > development resources and maintenance of the new lib, does this pay off? > > Am Montag, 18. März 2013 06:19:33 UTC+1 schrieb Prajwal Manjunath: >> >> Hi, >> >> I was reading up on writing addons for Node. I realize its primary >> purpose is to extend Node's functionality, but I was wondering, if my >> application uses a C++ library very frequently, would I get any performance >> benefit by binding it to the V8 runtime with node-gyp, versus just calling >> it through command line? >> > -- -- 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.
