It's working great but odbc to db2 queues and backs up some. I assume because when using ps -eLf I can see that there are still only 4 threads per node and the number doesn't change.
Is the thread count suppose to change dynamically with libuv now? On Friday, January 4, 2013 11:20:31 AM UTC-5, Ben Noordhuis wrote: > > On Thu, Jan 3, 2013 at 11:57 PM, am_p1 <[email protected]<javascript:>> > wrote: > > ok, so apparently eio is gone and libuv is what i'm actually using (not > > knowing the history of node makes for a confusing day) > > > > no wonder eio or eio-simple didn't work :-) > > > > so I couldn't find any min/max controls on threads anywhere so i assume > that > > if i'm seeing queuing, my only choice is another node (or > > child_process.fork) ? > > > > thanks for the advice!! > > Yes, libev and libeio are gone. libuv doesn't let you set upper or > lower bounds on its thread pool's size, it's supposed to Just Work. > > Forking is a pretty good strategy; I would recommend it over mucking > around with thread pools. > -- 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
