It would be a lot better if you could isolate the problem and provide a 
snippet. Normally you shouldn't experience this problem, so there must be 
something wrong with the code.

On Tuesday, August 19, 2014 3:43:51 PM UTC+3, manjunath wrote:
>
> we have the following scenario and we are greatly stuck to scale it and 
> cannot find the problem
>
> our processflow is as follows:
> -request received from client and headers are collected
> -initiate a async.waterfall
> >>get some data from redis
> >>build some object based on redis
> >>build an array of tasks for async.parallel to send requests to 3-5 
> servers
> >>run a async.parallel using above tasks
> >>>>if the async.parallel got some results in any of the request sent in 
> parallel, send that to client and end(header is set to connection:close for 
> client)
> >>>>if not then run an async.waterfall to send requests to different set 
> of servers one after another in a synchronous manner, we are waiting for 
> one to close before other one is initiated(wait.for is used with fibers)
> >>>>>>same here if there is some result from request in waterfall then 
> send it to client and end
>
> we are trying to hit this to concurrency at 200(having plans to increase 
> to 2000) but still failing, we are facing gradual increase in the response 
> time from our system
> we are using cluster also in this app, we have a guess this might be due 
> to sockets issue, can anyone help us out.
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/247cefbb-8aac-4d05-9222-4a5e5adb91a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to