Are you sure you have 100 rows in your prod_master? try to replace query 
with "select * from prod_master limit 100"
200 rps seems to be too low for 100 rows of data

On Saturday, 21 February 2015 06:29:16 UTC+11, Anirban Bhattacharya wrote:
>
> So,
>
> I made changes to code of node.
>
> 1. I removed that extra query for use data base and added in connect 
> paarmeter.
> 2. I changed it to createPool. But still the siege output is awkward
>
> See in node (the upper one) 
> 1. The number of hits and transactions is less than that of PHP+Apache
>  in node it is 119171 and for php+apache it is 119429
> 2. Longest transaction is more in node than PHP
>
>
> Why is so? What will be a good basic scenario which can show me NODe has 
> better values for these
>
> ====================================================After Doing 
> pool==============================================
> anirbanb2004@Anisoft-Corporation:~/nodecode/express/siegeLog$ siege -c100 
> -d1 -t10M -lnode.log http://localhost:9615/
> ** SIEGE 3.0.5
> ** Preparing 100 concurrent users for battle.
> The server is now under siege...
> Lifting the server siege...      done.
>
> Transactions:              119171 hits
> Availability:              100.00 %
> Elapsed time:              599.32 secs
> Data transferred:          402.78 MB
> Response time:                0.00 secs
> Transaction rate:          198.84 trans/sec
> Throughput:                0.67 MB/sec
> Concurrency:                0.67
> Successful transactions:      119171
> Failed transactions:               0
> Longest transaction:            0.10
> Shortest transaction:            0.00
>  
> FILE: node.log
>
> anirbanb2004@Anisoft-Corporation:~/nodecode/express/siegeLog$ siege -c100 
> -d1 -t10M -lphp.log http://localhost/loadTest/
> ** SIEGE 3.0.5
> ** Preparing 100 concurrent users for battle.
> The server is now under siege...
> Lifting the server siege...      done.
>
> Transactions:              119429 hits
> Availability:              100.00 %
> Elapsed time:              599.04 secs
> Data transferred:           58.77 MB
> Response time:                0.00 secs
> Transaction rate:          199.37 trans/sec
> Throughput:                0.10 MB/sec
> Concurrency:                0.36
> Successful transactions:      119429
> Failed transactions:               0
> Longest transaction:            0.04
> Shortest transaction:            0.00
>  
> FILE: php.log
>
>
> On Wednesday, February 18, 2015 at 3:34:57 PM UTC-6, Anirban Bhattacharya 
> wrote:
>>
>> Hi,
>> I am new to node. very new ..like infant.
>> Either I am doing something wrong or I understood everything wrong.
>> I wrote a node js simple JSON emitter which uses mysql module and query 
>> (select *) from a single table haviing 100 records and outputs on page as 
>> JSON (JSON.stringify..
>>
>> I wrote a PHP page which also does the same thing from same table(Apache).
>>
>> I used Siege for load test and surprisingly it shows better values for 
>> the PHP than that of node .. see below the output of siege
>> ==================NODE=================
>> anirbanb2004@Anisoft-Corporation:~$ siege -c100 -d1 -t10M -lnode.log 
>> http://localhost:9615/
>> ** SIEGE 3.0.5
>> ** Preparing 100 concurrent users for battle.
>> The server is now under siege...
>> Lifting the server siege...      done.
>>
>> Transactions:              119236 hits
>> Availability:              100.00 %
>> Elapsed time:              599.74 secs
>> Data transferred:          403.00 MB
>> Response time:                0.00 secs
>> Transaction rate:          198.81 trans/sec
>> Throughput:                0.67 MB/sec
>> Concurrency:                0.61
>> Successful transactions:      119236
>> Failed transactions:               0
>> Longest transaction:            0.05
>> Shortest transaction:            0.00
>>  
>> FILE: node.log
>> =================PHP==================
>> anirbanb2004@Anisoft-Corporation:~$ siege -c100 -d1 -t10M -lphp.log 
>> http://localhost/loadTest
>> ** SIEGE 3.0.5
>> ** Preparing 100 concurrent users for battle.
>> The server is now under siege...
>> Lifting the server siege...      done.
>>
>> Transactions:              119632 hits
>> Availability:              100.00 %
>> Elapsed time:              599.47 secs
>> Data transferred:           34.58 MB
>> Response time:                0.00 secs
>> Transaction rate:          199.56 trans/sec
>> Throughput:                0.06 MB/sec
>> Concurrency:                0.12
>> Successful transactions:       59858
>> Failed transactions:               0
>> Longest transaction:            0.03
>> Shortest transaction:            0.00
>>  
>> FILE: php.log
>>
>> can anyone please help me understand what is wrong here? I understand 
>> some scenario will be there where PHP will perform better. What scenario 
>> should I create to test Node is better?
>>
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/6485cb94-5ea3-4ea9-9416-0e0413f19bf1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to