On Mon, Nov 26, 2012 at 07:15:57PM -0800, Barry Steyn wrote: > Hi All > > We attempted to benchmark nodejs against python by using the express > framework (for Node) versus flask framework (for Python). The idea was to > use basic auth on a database with ten thousand (10,000) usernames. The > database table that holds the usernames was not optimised in any way (i.e. > no indexes etc). > > We expected (and hoped) for NodeJS to outperform Python due to the heavy IO > load in the test. Unfortunately, the results were almost the same, with > Python slightly beating Node. We were also noticing that response times > across both were varying quite a bit (from ~50/sec to ~500/sec)... perhaps > there's something else we're missing.
What tools were you using for testing? What are the potential bottlenecks with your approach to the task at hand? Are the tools you're using suited to the tasks and approach you're using? Are you controlling for memory allocation? How much paralellism? How much allocation in the hot paths? How long lived are the requests? Can the database or database driver be serializing things unexpectedly? What's your concurrency? What's the significance of the variation in timing? Are you testing locally or across a network? Did your micro instance get CPU throttled? Do you have metrics that would let you know?
pgp4pc7awZ2Q9.pgp
Description: PGP signature
