I was unable to get linux-tick-processor running on Ubuntu 13.04. And googling for errors didn't help either.
So I ended up rewriting the application in pure C using excellent, brilliant libuv. So the resulting application is able to saturate 100Mbit network within a single process using no more than 2-3% CPU time and a tiny fraction of RAM. Guess node.js wasn't the best choice for a port forwarder tool :-) On Wednesday, July 3, 2013 5:56:37 PM UTC+3, Ben Noordhuis wrote: > > On Wed, Jul 3, 2013 at 4:10 PM, Egor Egorov <[email protected]<javascript:>> > wrote: > > Hello. > > > > I've got a server running 8 instances of a simple "port forwarder" > written > > in node.js using .pipe(). I'm running 0.10.12 and I have coded the > service > > using the 0.10 streams ('readable' event and .data()). The server is > running > > latest debian. > > > > When the total network throughput on the server gets over about 60 > mbits, > > all instances consume 100% CPU. In total I .pipe() about 3k connections > on a > > server. > > > > What are my options to optimize raw network performance? > > Profile your application first (--prof --log) and run the v8.log files > through deps/v8/tools/linux-tick-processor. > > Make sure that each process writes to its own v8.log or you will get > bogus numbers. The cluster module takes care of that for you. If > you're using the child_process module, spawn each process with { > execArgv: ['--logfile=v8-%p.log'] }. > -- -- 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.
