Haven't run your code on mine (and what I'm going to say is all theoretical) but you'd need to ensure your tcp stack is optimised to minimise latency even when using a loopback interface. You still have the overhead of TCP (congestion control, flow control, stream management, IP packet ordering, retransmission, etc). I wouldn't have expected the beaglebone to be significantly worse/better in this respect.
This article is quite nice http://techblog.netflix.com/2014/11/nodejs-in-flames.html and so perhaps we could use some of that to profile what's going on within Node.js itself. On Monday, March 30, 2015 at 1:59:37 PM UTC+1, Matthew Karas wrote: > > The log I'm getting from this example app shows a minimum response time of > 4 - 17 ms. The route itself is doing nothing. Is this the quickest > response node can do on the bbb? The board is only running the example > server. > > GET / 200 16.876 ms - 0 > GET / 200 4.474 ms - 0 > GET / 200 4.592 ms - 0 > GET / 200 4.375 ms - 0 > GET / 200 4.858 ms - 0 > GET / 200 4.613 ms - 0 > GET / 200 4.588 ms - 0 > GET / 200 4.397 ms - 0 > GET / 200 4.667 ms - 0 > GET / 200 4.406 ms - 0 > > > Current experiment code > > var express = require('express'); > var app = express(); > > app.configure(function() { > app.use(express.logger('dev')); > }); > > app.get('/', function (req, res) { > res.send('') > }) > > var server = app.listen(3000, '0.0.0.0', function () { > > var host = server.address().address > var port = server.address().port > > console.log('Example app listening at http://%s:%s', host, port) > > }) > > > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" 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/d/optout.
