So I'm seeing some queuing in my odbc to db2 path, I assume due to the note on node-odbc's npm page re 4 threads (pretty sure queuing not related to hardware right now).
The note also implies this area is changing with node 0.10 (I'm at 0.8.16). I'm trying to determine some general rules of thumb when you should/shouldn't use multiple node's vs more threads with a single node. My noobie take on this is (since running parallel is fine with my app/db design) to spread as many nodes wide as I need, until the hardware starts queuing somewhere. Partly because child_process.fork says "That is, you cannot create many thousands of them", which implies to me I can create hundreds. :-) -- 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
