Re: [nodejs] os.cpus() and times

2014-12-07 Thread Christopher Rust
I can't comment on how cpu idle time is calculated or if the cpus() array is consistently ordered but I can point out that setTimeout is not expected to be perfectly accurate. >From the http://nodejs.org/api/timers.html";>documentation: "It is important to note that your callback will probably no

Re: [nodejs] os.cpus() and times

2014-12-07 Thread // ravi
On Dec 7, 2014, at 11:06 PM, // ravi wrote: > > > I am stumped by what must clearly be a misreading on my part. Node 0.10 docs > say that each element of os.cpus() contains information about each CPU/core. > This information includes "the number of milliseconds the CPU/core spent in: > user,

Re: [nodejs] What's the best version of npm to use?

2014-12-07 Thread Sam Roberts
IMO, npm1 from node v0.10 works ok on linux/os x. On Windows, though, I'd say npm2 is mandatory. I consistently see Windows issues cleared away by updating to npm2, major bugs were fixed. -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-modera

[nodejs] os.cpus() and times

2014-12-07 Thread // ravi
Hello all, I posted this question on node-forward/help on Gitter, so apologies if you are seeing this again. I am stumped by what must clearly be a misreading on my part. Node 0.10 docs say that each element of os.cpus() contains information about each CPU/core. This information includes "the

Re: [nodejs] node.js and io.js reconciliation

2014-12-07 Thread // ravi
I appreciate your detailed response Forrest. Perhaps it would also help to clarify what to expect and where to go for help. Example: Use: * joyent/node GitHub issues for confirmed bugs in Node core * This list for discussion of general Node issues, technical and otherwise * Gitter for quick on

Re: [nodejs] Some questions on Node's threading and scaling.

2014-12-07 Thread Aria Stewart
> On 7 Dec 2014, at 05:31, Harry Simons wrote: > > Aria, Julien - those were very enlightening answers! Looks like, I'll be > busy for a few months now digging into this area. I'm incidentally new to web > application development, too. Though I'll be making Node/Express my first web > applic

Re: [nodejs] What's the best version of npm to use?

2014-12-07 Thread Aria Stewart
To answer quickly: the latest. Take all advice for 'best practices' with a huge lump of salt because 'best' depends on the context. There is no one best. > On 7 Dec 2014, at 01:06, J Irving wrote: > For any given version of node, what's the best, most appropriate, and least > likely to be prob

Re: [nodejs] Some questions on Node's threading and scaling.

2014-12-07 Thread Harry Simons
Aria, Julien - those were very enlightening answers! Looks like, I'll be busy for a few months now digging into this area. I'm incidentally new to web application development, too. Though I'll be making Node/Express my first web application development platform/framework, I won't have the bene

Re: [nodejs] node.js and io.js reconciliation

2014-12-07 Thread Boris Matos Morillo
Thanks for your response. I'll keep waiting what happens in the next weeks, hoping all of this comes with a solution that is satisfactory for everyone. -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: htt

[nodejs] What's the best version of npm to use?

2014-12-07 Thread J Irving
Hi This is a "best practices" question, motivated by the need to test against many versions of node. For any given version of node, what's the best, most appropriate, and least likely to be problematic version of npm to use? Node ships with npm, so I'm inclined to just use the version of npm w