Hi, We've experienced some high latency with a Django project using mod-wsgi in daemon mode. That web service does folder management ... and has a /refresh POST url that will keep the request hang until a) a change is made in the folder or b) 60 seconds have passed.
With this, having a few clients ... already used the 15 threads available. And any new request were waiting for a /refresh to timeout before being processed. I guess such /refresh method is not today's best practice ... and the dev (me) would better look into XHR calls (which I don't know yet). With this, I have 3 questions : + Would XHR calls be non-consuming threads as POST do? + How to best size today's solution? Since all /refresh are spending their time doing some DB requests followed by `time.sleep(1)` ... Can I grow the number of threads to 256? Or shall I split it to something like 8 processes of 32 threads? (or even above?) + Before that, we used mod-wsgi in embedded mode ... which never gave any latency we could measure. Would it be, for such situation, better to switch back to embedded mode? Thanks, Samuel Bancal -- 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 https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
