Hi, But having a lot of different events, like many users pulling pages at > once, would give a bad result in that test.
I'm not claiming it's sophisticated :) and you're right, in that the indicated latency will be the aggregate of a number of queued events, not just a single event. But nonetheless it does give an indication of the time between, say, an FD becoming readable and a handler being called with the data, which is the measure of latency that matters to your app. Thanks - paddy -- 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
