Oh well, thanks for your responses so far. If anyone has any real world experiences with scaling and using nodeJS, I would be interested in how you set up things computationally.
Did you actually have the nodeJS perform work? Or just fetch results? If just fetch results, what did you use on your back end? Especially, did you even use a framework? For instance I can see having maybe 50 workers in java/c#/c++ sitting on queues, waiting for requests and feeding them back results. But, I'm interested in what someone says who has actually done it. -tim On Tuesday, April 10, 2012 5:57:01 PM UTC-4, timp wrote: > > (I think) I just tried the native bson with the pages > > or at least I did this: > > pm install mongodb --mongodb:native > seemed to compile things > > the mongoskin says it will use it if it is there > > tests are coming out about the same. +/- 5 fps > > > On Tuesday, April 10, 2012 5:46:38 PM UTC-4, Jann Horn wrote: >> >> Am Dienstag, den 10.04.2012, 10:15 -0700 schrieb timp: >> > But at the same time, I am truly annoyed at how slow these web >> > servers/frameworks are. >> >> Me too. :D >> >> I have a small node.js proxy running here, and even when it's just >> piping through a youtube video (using the normal Stream pipe method) >> between the browser and youtube, nodes CPU usage goes way over 10%. It >> takes half of what flash uses. >> >> Well, and if you look closer, you can see that e.g. 15% of the time are >> spend with write completion callbacks which are probably nearly never >> used. Still, each completed write means that there's a call from C++ >> land into JS land, a bunch of JS code and a call from JS to C++ (resume >> input). >> >> On Tuesday, April 10, 2012 5:57:01 PM UTC-4, timp wrote: > > (I think) I just tried the native bson with the pages > > or at least I did this: > > pm install mongodb --mongodb:native > seemed to compile things > > the mongoskin says it will use it if it is there > > tests are coming out about the same. +/- 5 fps > > > On Tuesday, April 10, 2012 5:46:38 PM UTC-4, Jann Horn wrote: >> >> Am Dienstag, den 10.04.2012, 10:15 -0700 schrieb timp: >> > But at the same time, I am truly annoyed at how slow these web >> > servers/frameworks are. >> >> Me too. :D >> >> I have a small node.js proxy running here, and even when it's just >> piping through a youtube video (using the normal Stream pipe method) >> between the browser and youtube, nodes CPU usage goes way over 10%. It >> takes half of what flash uses. >> >> Well, and if you look closer, you can see that e.g. 15% of the time are >> spend with write completion callbacks which are probably nearly never >> used. Still, each completed write means that there's a call from C++ >> land into JS land, a bunch of JS code and a call from JS to C++ (resume >> input). >> >> On Tuesday, April 10, 2012 5:57:01 PM UTC-4, timp wrote: > > (I think) I just tried the native bson with the pages > > or at least I did this: > > pm install mongodb --mongodb:native > seemed to compile things > > the mongoskin says it will use it if it is there > > tests are coming out about the same. +/- 5 fps > > > On Tuesday, April 10, 2012 5:46:38 PM UTC-4, Jann Horn wrote: >> >> Am Dienstag, den 10.04.2012, 10:15 -0700 schrieb timp: >> > But at the same time, I am truly annoyed at how slow these web >> > servers/frameworks are. >> >> Me too. :D >> >> I have a small node.js proxy running here, and even when it's just >> piping through a youtube video (using the normal Stream pipe method) >> between the browser and youtube, nodes CPU usage goes way over 10%. It >> takes half of what flash uses. >> >> Well, and if you look closer, you can see that e.g. 15% of the time are >> spend with write completion callbacks which are probably nearly never >> used. Still, each completed write means that there's a call from C++ >> land into JS land, a bunch of JS code and a call from JS to C++ (resume >> input). >> >> -- 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
