My intent was same. I load test my app and increases the load successively.
when it reaches to 10000 or above, a latency of more than 1sec is
introduced (as CPU shoot up) which is not acceptable.
so at this point my app is behaving like accepting 10000 req/s.
On Tuesday, February 18, 2014 3:57:20 PM UTC+5:30, Nitin Gupta wrote:
>
> Hi, This is regarding scaling node.js application. I have heard a lot of
> buzz around handling millions of connection by single node.js server.
>
> To check that i wrote a http server which was returning nothing but 200 ok
> and CPU started blowing up with 10000 concurrent requests.
>
> CODE:
> my_http.createServer(function(request, response){
> response.writeHead(200);
> response.end();
> });
>
> I have an application which has to handle 1M concurrent connections but
> what i found with testing doesn't seem like a solution to this. Please
> guide me through this. Have i missed something or is it not possible with
> barebone node.js server.
>
> My application looks like:
> a.) MongoDB with node.js
> b.) A post request with some params.
> c.) Saving params' values to DB and return to client with success or
> failure
>
>
--
--
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
---
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
