Performance is certainly going to be a big focus as we move forward with the code base, but we're not quite there yet.
It is too early to do performance testing - the whole team is focused on function. The changes we needed to make to the Node.js code base are minimal (trivial), if you go peek at the repository https://github.com/andrewlow/node you can see they are focused on a couple of endian issues and simply tweaking the GYP scripting to allow it to build with the right options. Of course that is ignoring the port of V8 to PowerPC. You can find the code embedded in the repository above, or look here for the latest version: https://github.com/andrewlow/v8ppc All the development we're doing is in the open, the GitHub repositories are the master code base the team is working against day to day. In terms of performance on PowerPC - there are going to be two large contributing factors. The quality of the code produced by GCC (and this may vary based on the level, there is the Advance Toolchain to consider here). The other factor is the V8 code (and quality) of the optimizations it performs. Lower down on the list will be tweaks to the openssl (assembly) and other open source projects that have optional assembly for optimization. There is still some low hanging fruit in our V8 port to PowerPC - we'll try to pick that sooner than later, but the real performance stuff is going to come after we've successfully got the V8 and Node code we've created adopted more broadly by the community - ideally we'll get our code into the master repositories making it easy for everyone to get it and help keep it current. This is by no means a closed project, the code is there on GitHub. Fork it. Log issues. Contribute patches. If you're looking for PowerPC resources to work with - consider http://osuosl.org/services On Tuesday, September 17, 2013 7:34:33 PM UTC-4, am_p1 wrote: > > Any benchmarks you can share? like on one of those 4.42 GHz POWER7+ chips? > > On Tuesday, September 3, 2013 2:41:53 PM UTC-4, Andrew Low wrote: >> >> Hi folks, allow me to introduce myself. I'm Andrew Low and I work for >> IBM. I've been building runtime technology for almost 20 years, over that >> time I've built Smalltalk VMs (http://en.wikipedia.org/wiki/IBM_VisualAge), >> Java VMs (http://en.wikipedia.org/wiki/IBM_J9), and I'm now working on >> JavaScript runtimes (and this means Node.js too!) >> >> Since early this year I've been leading a small team porting V8 to >> PowerPC. If you're keen to follow along all of our work it up on GitHub >> https://github.com/andrewlow/v8ppc >> >> As most of you are aware, Node.js relies on V8 for it's javascript >> runtime. This has been a barrier to bringing Node.js to platforms that >> don't (yet) have a V8 port. Now that the V8 port to PowerPC is fairly >> feature complete, we're able to bring Node.js up on Power Linux. You can >> check the code out here: https://github.com/andrewlow/node - >> specifically the branch "v0.10.16-release-ppc" >> >> We're planning on giving all of this code back to the community - it's >> all there on GitHub now and licensed in the same manner as the original >> project. So far there are only a handful of changes to the Node.js code. >> >> There is also a public Jenkins continuous integration server building >> binaries: http://v8ppc.osuosl.org:8080/ >> >> Limitations: For now it's only 32bit (but the binaries will of course run >> just fine on 64bit systems). We're also stuck on the 0.10.x branch of Node >> for the time being. We will be working towards removing these limitations. >> > -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
