Memory Usage

[vitaly-t]

I'm still testing iojs vs nodejs in terms of memory consumption, without expecting much difference, but from what I see, even when you just run the process without any parameters, you get immediate difference:

NodeJS, 64-bit, Win 8.1 (0.10.36): 5.1MB
ioJS, 64-bit, Win 8.1: (1.2.0): 7.4MB

Is this a justifiable change in the initialization code to consume extra 45% of memory at start? Or is it something to be concerned about?

[Fishrock123]

@VitalyTomilov can you compare against node 0.12? Most of the difference comes from the bumped v8 version, external memory allocation changes, etc, that were done in 0.11.x.

(besides, there are many reasons related to v8 itself that this sort of memory usage is a bad measurement of anything.)

[targos]

node 0.12 consumes more memory than io.js ;)

@VitalyTomilov Do you plan to have so many iojs processes running at the same time that this initial difference becomes a problem?

[vitaly-t]

Ok, Node 0.12.0 seems to consume initially 2% more memory than IO 1.2.0 - that's good 👍 Must be the latest V8 indeed.

I'm a newcomer here, dunno enough about the project yet. When I tried to do a change over for an existing project, I couldn't get GruntJS to install and work as expected, so had to roll back. Still don't know how to do that, and I got all my projects with Grunt JS. I know I digress, but any suggestions are welcome.

The question that troubles me most - if my app has a problem building under Node 0.12.0 (as opposed to 0.10.36), does this mean it will most likely have the same issue when using IO 1.2?

[Fishrock123]

@VitalyTomilov correct. If your app runs on 0.12, it should run on io.js.

Are you getting any errors? I can take questions here, or in #io.js on freenode, but some output / code / something is most helpful. :)