How many client threads are you pushing from JMeter?  Node can't really 
outperform if its getting the same number of client threads and they're all 
sitting around waiting for the DB to do a full table scan.  As a side note, 
I would assume the variance in your response times is dependent on where 
the target row in the DB is.  Since you have no index, the query would have 
to look at each row.  If it finds it early, then quick response time.  If 
it finds it near the end, then longer response time.  That's my initial gut 
reaction to how your test would behave anyway.

On Monday, November 26, 2012 10:15:57 PM UTC-5, 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.
>
> The setup was as follows:
>
>    - Web server: NginX
>    - For Python: Uwsgi server with 30 threads
>    - For node: Just ran node app on the command line
>    - A micro instance of AWS running unbuntu 12.04
>
> Why is Node's performance not blowing Python out of the water. Perhaps we 
> have done something wrong with our benchmarking test. Any ideas would be 
> appreciated.
>
> Barry And Niall
>
>

-- 
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

Reply via email to