As Graham says, we need to see the config. Just FYI, I regularly benchmark nginx + apache + mod_wsgi at 4,000 requests per second using a test application. It is really fast when configured correctly.
On Thu, Oct 30, 2014 at 11:00 PM, Minh Tuan <[email protected]> wrote: > oh anyway, forget the complicated api, i just make the app that just sleep > 1.02 second then return a default value. The overall response still 6 sec > too at 150 concurrent requests. > > Minh Tuan. > > On Fri, Oct 31, 2014 at 9:53 AM, Minh Tuan <[email protected]> wrote: > >> Thanks Jason for the response, >> I'm using daemon mode with 6 processes and 5 threads. My server is HP >> gen7 with 24 core and 12GB RAM. >> I had measured the time from api call start to the end at 150 concurrent >> requests, it's always around 1 + 0.02 sec. Don't know how to calculate at >> start of request, just refer to siege result and actual experience that the >> response average is 6 sec. >> So, seem the requests are queued to wait for other ones complete. Should >> i change to 10 processes and 15 threads? >> >> P/S: i temporarily assume the external web service that i call api to can >> handle this load cause it is IN production by Comverse which serve the >> charging activities for entire of Mobile Operator business. >> >> Minh Tuan. >> >> On Fri, Oct 31, 2014 at 1:16 AM, Jason Garber <[email protected]> wrote: >> >>> You have not mentioned if you are in daemon mode or embedded mode. I'll >>> assume Daemon Mode, and if you are not already, maybe switching is a good >>> idea. >>> >>> Assuming the external web service can handle the load you are throwing >>> at it (which isn't something we should do), then the issue perhaps has to >>> do with your processes and threads configuration. Unless you have 10 >>> processes with 15 threads, and enough oomph on your server to handle that, >>> then your requests are going to be backlogged while the others complete. >>> >>> Suggest you write the request start, api call start, processing start, >>> and processing end time to a log file for each request, and then see what >>> is really happening. >>> >>> >>> On Thu, Oct 30, 2014 at 11:29 AM, Ice Prince <[email protected]> >>> wrote: >>> >>>> Hello again, >>>> I'm getting a situation related to my application performance that out >>>> of my knowledge. >>>> In short, my app has 2 steps: first, queries a external web service to >>>> retrieve some data and the second, process that data and return the result. >>>> For every single request, the 1st step takes 0.18 sec and the 2nd step >>>> takes 0.02 sec for average, so it takes 0.2 sec in total to serve an single >>>> request. (just put a time measurement in code to get these numbers) >>>> And if i using: *siege -i -d1 -c1 http://my_applition >>>> <http://my_applition> * , the "Response time:" also is *0.2sec* too. >>>> >>>> Now the issue happens if i run: *siege -i -d1 -c150 >>>> http://my_applition <http://my_applition> , *the 1st step which >>>> queries external web service increase the time consumption to 1sec (i'm not >>>> sure it is overloaded or not), the 2nd step still the same 0.02sec as >>>> normal, but overall, my app become slowly and the "Response time:" by siege >>>> show the result is *6sec*. >>>> >>>> I don't know which progress consume my time, please help me an idea. >>>> Thanks in advance. >>>> >>>> Minh Tuan. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "modwsgi" 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]. >>>> Visit this group at http://groups.google.com/group/modwsgi. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "modwsgi" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/modwsgi/j52MhsN4JfI/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/modwsgi. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> <====((=o-( ',_,' )-o=))=====> >> >> Bản chất tốt nhưng cuộc đời xô đẩy! >> > > > > -- > <====((=o-( ',_,' )-o=))=====> > > Bản chất tốt nhưng cuộc đời xô đẩy! > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" 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]. > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "modwsgi" 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]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
