[nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-05 Thread Erik Dubbelboer
I wrote a small module to be able to set the number of threads in javascript. https://github.com/ErikDubbelboer/node-eio-simple I'll start doing some real life tests with it soon. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting

[nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-02 Thread Liam
On Mar 2, 5:47 am, Ben Noordhuis wrote: > > Maybe I should've mentioned that I'm mostly interested in file I/O, > that still being something of a weak spot in Node. :-) Well one common file i/o op would be improved by enabling sendfile() to a socket :-) Also, there was this discussion of file

Re: [nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-02 Thread Erik Dubbelboer
On Friday, March 2, 2012 5:11:04 PM UTC+1, Jorge wrote: > > > Please note that time passes in parallel (N threads doing usleep()s in > parallel are always going to be faster than M< usleep()s), but real disk I/O jobs even when ran in parallel in separate > threads tend to be executed sequentiall

Re: [nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-02 Thread Jorge
On Mar 2, 2012, at 2:14 PM, Erik Dubbelboer wrote: > On Thursday, March 1, 2012 11:50:21 PM UTC+1, Ben Noordhuis wrote: > On Thu, Mar 1, 2012 at 22:16, Erik Dubbelboer wrote: > > Hi Everyone, > > > > I was wondering what the status is for this API. I couldn't find anything in > > the current doc

Re: [nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-02 Thread Ben Noordhuis
On Fri, Mar 2, 2012 at 14:14, Erik Dubbelboer wrote: > On Thursday, March 1, 2012 11:50:21 PM UTC+1, Ben Noordhuis wrote: >> >> On Thu, Mar 1, 2012 at 22:16, Erik Dubbelboer wrote: >> > Hi Everyone, >> > >> > I was wondering what the status is for this API. I couldn't find >> > anything in >> > t

Re: [nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-02 Thread Erik Dubbelboer
On Thursday, March 1, 2012 11:50:21 PM UTC+1, Ben Noordhuis wrote: > > On Thu, Mar 1, 2012 at 22:16, Erik Dubbelboer wrote: > > Hi Everyone, > > > > I was wondering what the status is for this API. I couldn't find > anything in > > the current documentation so I'm guessing it hasn't been implemen

Re: [nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-02 Thread Erik Dubbelboer
On Thursday, March 1, 2012 11:50:21 PM UTC+1, Ben Noordhuis wrote: > > On Thu, Mar 1, 2012 at 22:16, Erik Dubbelboer wrote: > > Hi Everyone, > > > > I was wondering what the status is for this API. I couldn't find > anything in > > the current documentation so I'm guessing it hasn't been implemen

Re: [nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-02 Thread Ben Noordhuis
On Fri, Mar 2, 2012 at 10:45, Erik Dubbelboer wrote: > Calling eio_set_min_parallel() from a module still seems to work (only on > unix I guess). What exactly has moved to libuv? All the platform-specific code. eio_set_min_parallel() still works because libuv is compiled without -fvisibility=hidd

Re: [nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-02 Thread Erik Dubbelboer
On Thursday, March 1, 2012 11:50:21 PM UTC+1, Ben Noordhuis wrote: > > On Thu, Mar 1, 2012 at 22:16, Erik Dubbelboer wrote: > > Hi Everyone, > > > > I was wondering what the status is for this API. I couldn't find > anything in > > the current documentation so I'm guessing it hasn't been implemen

Re: [nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-01 Thread Ben Noordhuis
On Thu, Mar 1, 2012 at 22:16, Erik Dubbelboer wrote: > Hi Everyone, > > I was wondering what the status is for this API. I couldn't find anything in > the current documentation so I'm guessing it hasn't been implemented yet? > > If this is the case I guess I could take a look at it since it would

[nodejs] Re: [PATCH] Add runtime accessor process.maxIOThreads

2012-03-01 Thread Erik Dubbelboer
Hi Everyone, I was wondering what the status is for this API. I couldn't find anything in the current documentation so I'm guessing it hasn't been implemented yet? If this is the case I guess I could take a look at it since it would really be nice to have this for machines with a lot of cores i