On Fri, Jan 4, 2013 at 5:41 PM, am_p1 wrote:
> 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
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,
On Thu, Jan 3, 2013 at 11:57 PM, am_p1 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 assu
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 anothe
left out that ALL node's would be long running (started just once in the
morning) so no startup/teardown overhead...
On Thursday, January 3, 2013 12:33:02 PM UTC-5, am_p1 wrote:
>
> 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
