[Flask] flask queue question

Ben De Luca bdeluca at gmail.com
Sun Jul 9 09:32:21 EDT 2017


Docker would be very easy. It's how we deploy our software on lin/win/Mac.
Don't have to think about what platform we are on then it's always Linux.

On Sat, 8 Jul 2017 at 1:51 am, Corey Boyle <coreybrett at gmail.com> wrote:

> Rita,
>
> I found the following article about deploying Django on IIS, purhaps you
> could adapt it to your needs.
>
>
> https://www.toptal.com/django/installing-django-on-iis-a-step-by-step-tutorial
>
>
>
>
> __
>
> Corey
>
> On Jul 7, 2017 9:57 AM, "Corey Boyle" <coreybrett at gmail.com> wrote:
>
>> mod_wsgi might be an option for you if you are willing to use Apache.
>>
>> https://github.com/GrahamDumpleton/mod_wsgi/blob/develop/win32/README.rst
>>
>> Otherwise, you might be better off setting up a Linux box.
>>
>> __
>> Corey
>>
>> On Jul 7, 2017 9:43 AM, "Rita" <rmorgan466 at gmail.com> wrote:
>>
>>> Right, when the client makes a request it gets forward to flask app. But
>>> the flask app is syncrnous so it will wait a long time. Ideally, I am
>>> looking for a good uWSGI (high performance) on Windows.
>>>
>>> On Fri, Jul 7, 2017 at 8:59 AM, Gergely Polonkai <gergely at polonkai.eu>
>>> wrote:
>>>
>>>> If you use an HTTP server, like nginx or Apache httpd, the story
>>>> changes a lot. In that case, it’s the HTTP server that handles the
>>>> connection and the requests. When the request is received, it is forwarded
>>>> to the Flask app, usually through a WSGI layer like uWSGI or Apache’s
>>>> mod_wsgi.
>>>>
>>>> On Fri, Jul 7, 2017, 14:54 Adil Hasan <paradox2005 at gmail.com> wrote:
>>>>
>>>>> Hello Rita,
>>>>> I wonder. Do you think that the nginx server is handling the requests?
>>>>> I think the webserver is the service that will manage requests. At
>>>>> least
>>>>> I think that it is.
>>>>> hth
>>>>> adil
>>>>>
>>>>> On Fri, Jul 07, 2017 at 06:33:23AM -0400, Rita wrote:
>>>>> > yes, i understand that. how come when i submit ten concurrent
>>>>> requests none
>>>>> > of them get lost and eventually finish? how is that maintained?
>>>>> >
>>>>> > On Fri, Jul 7, 2017 at 3:19 AM, Abdesslem Amri <
>>>>> amriabdesslem at gmail.com>
>>>>> > wrote:
>>>>> >
>>>>> > > Using the simple app.run() from within Flask creates a single
>>>>> synchronous
>>>>> > > server on a single thread capable of serving only one client at a
>>>>> time.
>>>>> > >
>>>>> > > 2017-07-07 3:02 GMT+02:00 Rita <rmorgan466 at gmail.com>:
>>>>> > >
>>>>> > >> Been using flask in my lab for the past few years. It just works.
>>>>> We
>>>>> > >> recently got some grad students and it seems we are seeing some
>>>>> slowness in
>>>>> > >> our flask applications running on Windows 2012 with enthought
>>>>> python.
>>>>> > >>
>>>>> > >> currently I am running it in a single threaded mode with nginx (
>>>>> > >>
>>>>> http://flask.pocoo.org/docs/0.12/deploying/wsgi-standalone/#proxy-setups
>>>>> ).
>>>>> > >> My question is: When 2 users hit my flask page, does it get
>>>>> blocked until
>>>>> > >> the first user finishes his request - it seems that the case. Is
>>>>> there a
>>>>> > >> way to view the "queue" length? How is this queue maintained, or
>>>>> is it done
>>>>> > >> by operating system networking stack?
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> --
>>>>> > >> --- Get your facts first, then you can distort them as you
>>>>> please.--
>>>>> > >>
>>>>> > >> _______________________________________________
>>>>> > >> Flask mailing list
>>>>> > >> Flask at python.org
>>>>> > >> https://mail.python.org/mailman/listinfo/flask
>>>>> > >>
>>>>> > >>
>>>>> > >
>>>>> > >
>>>>> > > --
>>>>> > > ------------------------------
>>>>> > >
>>>>> > > The preceding message (including attachments) is covered by the
>>>>> Electronic
>>>>> > > Communication Privacy Act, 18 U.S.C. sections 2510-2512, is
>>>>> intended only
>>>>> > > for the person or entity to which it is addressed, and may contain
>>>>> > > information that is confidential, protected by attorney-client or
>>>>> other
>>>>> > > privilege, or otherwise protected from disclosure by law. If you
>>>>> are not
>>>>> > > the intended recipient, you are hereby notified that any retention,
>>>>> > > dissemination, distribution, or copying of this communication is
>>>>> strictly
>>>>> > > prohibited. Please reply to the sender that you have received the
>>>>> message
>>>>> > > in error and destroy the original message and all copies.
>>>>> > >
>>>>> > > _______________________________________________
>>>>> > >
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > --- Get your facts first, then you can distort them as you please.--
>>>>>
>>>>> > _______________________________________________
>>>>> > Flask mailing list
>>>>> > Flask at python.org
>>>>> > https://mail.python.org/mailman/listinfo/flask
>>>>>
>>>>> _______________________________________________
>>>>> Flask mailing list
>>>>> Flask at python.org
>>>>> https://mail.python.org/mailman/listinfo/flask
>>>>>
>>>>
>>>
>>>
>>> --
>>> --- Get your facts first, then you can distort them as you please.--
>>>
>>> _______________________________________________
>>> Flask mailing list
>>> Flask at python.org
>>> https://mail.python.org/mailman/listinfo/flask
>>>
>>> _______________________________________________
> Flask mailing list
> Flask at python.org
> https://mail.python.org/mailman/listinfo/flask
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/flask/attachments/20170709/1ed57626/attachment.html>


More information about the Flask mailing list