Re: Explain how to start / stop / restart tornado web server under Ubuntu !

[Thom Simmons]

It depends on your particular setup. If you use something like the
supervisord-based configuration [found here:
http://www.jeremybowers.com/blog/4/tornado-web-framework-production-django-and-nginx/]
then you would start/restart supervisord to manage the tornado
processes.

On Dec 1, 6:23 pm, "Md. Meshkatul Anwer" <meshkat...@gmail.com> wrote:
> Plz Explain how to start / *stop* / restart tornado *web server* under *Ubuntu
> !*

[rtg]

Hi Thom,

what is the main advantage to use nginx+tornado+django as a stack?

Thx, RTG

On 6 Dez., 13:19, Thom Simmons <t...@sliceofpi.com> wrote:
> It depends on your particular setup. If you use something like the

> supervisord-based configuration [found here:http://www.jeremybowers.com/blog/4/tornado-web-framework-production-d...]

[Thom Simmons]

I would say that, simply put, tornado is faster server than the alternatives & wrapping django in tornado is quite easy.

I am migrating my production servers to this stack because the perfornance is that good. I am also looking into building a django-native interface to tornado.

I'll put together more info soon.

Thom Simmons
Slice of Pi, LLC
CTO/Lead Developer
-- Sent from my Palm Prē

---

[rtg]

Thanks Thom,

but isn't django the dead end, since the instances are configured
statically. What I mean is, you make sure that you request
distribution is non blocking, but finally django is a blocking dead
end.
So you basically add up more latency to the request by routing it
through tornado, why not let nginx distribute the requests directly.
I understand the setup if there are routings which are handeled by
tornado, but as soon as it goes to django the whole advantage of
tornado is is not used?
Am I missing something?

RTG


On 7 Dez., 11:16, "Thom Simmons" <t...@sliceofpi.com> wrote:
> I would say that, simply put, tornado is faster server than the alternatives &amp; wrapping django in tornado is quite easy.

>
> I am migrating my production servers to this stack because the perfornance is that good. I am also looking into building a django-native interface to tornado.
>
> I'll put together more info soon.
>
> Thom Simmons
> Slice of Pi, LLC
> CTO/Lead Developer

> -- Sent from my Palm Prērtg wrote:
>
> Hi Thom,
>
> what is the main advantage to use nginx+tornado+django as a stack?
>
> Thx, RTG
>

> On 6 Dez., 13:19, Thom Simmons &lt;t...@sliceofpi.com> wrote:
>
> > It depends on your particular setup. If you use something like the
> > supervisord-based configuration [found here:http://www.jeremybowers.com/blog/4/tornado-web-framework-production-d...]
> > then you would start/restart supervisord to manage the tornado
> > processes.
>

[Thom Simmons]

You are right but I'm seeing a performance benefit that makes me want to use tornado. Of course, my development direction is to tie in tornado to django on a lower level to take advantage of its features. My goal is a nonblocking system though I haven't completely determined what is involved with that yet.

Thom Simmons
Slice of Pi, LLC
CTO/Lead Developer
-- Sent from my Palm Prē

[rtg]

Thanks Thom,

I am curios about your results with django integration.
Would be interesting to know if django people are planning to wire
tornado with django.

RTG

On 7 Dez., 11:31, "Thom Simmons" <t...@sliceofpi.com> wrote:
> You are right but I'm seeing a performance benefit that makes me want to use tornado. Of course, my development direction is to tie in tornado to django on a lower level to take advantage of its features. My goal is a nonblocking system though I haven't completely determined what is involved with that yet.
>
> Thom Simmons
> Slice of Pi, LLC
> CTO/Lead Developer

> -- Sent from my Palm Prērtg wrote:
>
> Thanks Thom,
>
> but isn't django the dead end, since the instances are configured
>
> statically. What I mean is, you make sure that you request
>
> distribution is non blocking, but finally django is a blocking dead
>
> end.
>
> So you basically add up more latency to the request by routing it
>
> through tornado, why not let nginx distribute the requests directly.
>
> I understand the setup if there are routings which are handeled by
>
> tornado, but as soon as it goes to django the whole advantage of
>
> tornado is is not used?
>
> Am I missing something?
>
> RTG
>

> On 7 Dez., 11:16, "Thom Simmons" &lt;t...@sliceofpi.com> wrote:
>
> > I would say that, simply put, tornado is faster server than the alternatives &amp;amp; wrapping django in tornado is quite easy.

>
> > I am migrating my production servers to this stack because the perfornance is that good. I am also looking into building a django-native interface to tornado.
>
> > I'll put together more info soon.
>
> > Thom Simmons
> > Slice of Pi, LLC
> > CTO/Lead Developer
> > -- Sent from my Palm Prērtg wrote:
>
> > Hi Thom,
>
> > what is the main advantage to use nginx+tornado+django as a stack?
>
> > Thx, RTG
>

> > On 6 Dez., 13:19, Thom Simmons &amp;lt;t...@sliceofpi.com> wrote:
>
> > > It depends on your particular setup. If you use something like the
> > > supervisord-based configuration [found here:http://www.jeremybowers.com/blog/4/tornado-web-framework-production-d...]
> > > then you would start/restart supervisord to manage the tornado
> > > processes.
>

[Thom Simmons]

There was talk about doing it before but nothing much seems to have come of it. I intend to build a supplemental library for django-tornado integration, however.

I'll be discussing this on my blog when I launch it next weekend on my sliceofpi.org domain

Thom Simmons
Slice of Pi, LLC
CTO/Lead Developer
-- Sent from my Palm Prē

[Matt F]

I like to think of Django as a web SITE framework, and Tornado as a
web APPLICATION framework.

To clarify, regardless of Django's innards, it gets deployed on
Tornado via the Tornado WSGI handler. WSGI doesn't support async
requests, so there's your dead end. There's no chance that Django
will be ported to work directly on Tornado without the WSGI wrapper;
its simply too large of a codebase and there are pieces that (despite
being 'loosely coupled') are not so loose.

Django is a great tool for designers to jump into the Python web
framework world, but a good share of these designers are hitting a
wall with Django, and are looking elsewhere for more flexibility. The
problem? No web framework out there is as simple to use or as well
documented as Django, and they get frustrated and give up. Sometimes
you need to do something your own way, and because of that, you end up
having to monkey patch around the magic. Which is not something most
designers want to do.

Tornado itself has so many great Djangoic pieces out of the box, that
I think all it would take is a more user-friendly ORM (SQLAlchemy or
one of its many declarative layers), the things that are essential to
Django (some of the different frameworks, middlewares, and the admin
piece), along with some great documentation, to make history.

But I could be wrong.

On Dec 7, 3:15 am, "Thom Simmons" <t...@sliceofpi.com> wrote:
> There was talk about doing it before but nothing much seems to have come of it. I intend to build a supplemental library for django-tornado integration, however.
>
> I'll be discussing this on my blog when I launch it next weekend on my sliceofpi.org domain
>
> Thom Simmons
> Slice of Pi, LLC
> CTO/Lead Developer

> -- Sent from my Palm Prērtg wrote:
>
> Thanks Thom,
>
> I am curios about your results with django integration.
>
> Would be interesting to know if django people are planning to wire
>
> tornado with django.
>
> RTG
>

> On 7 Dez., 11:31, "Thom Simmons" &lt;t...@sliceofpi.com> wrote:
>
>
>
> > You are right but I'm seeing a performance benefit that makes me want to use tornado. Of course, my development direction is to tie in tornado to django on a lower level to take advantage of its features. My goal is a nonblocking system though I haven't completely determined what is involved with that yet.
>
> > Thom Simmons
> > Slice of Pi, LLC
> > CTO/Lead Developer
> > -- Sent from my Palm Prērtg wrote:
>
> > Thanks Thom,
>
> > but isn't django the dead end, since the instances are configured
>
> > statically. What I mean is, you make sure that you request
>
> > distribution is non blocking, but finally django is a blocking dead
>
> > end.
>
> > So you basically add up more latency to the request by routing it
>
> > through tornado, why not let nginx distribute the requests directly.
>
> > I understand the setup if there are routings which are handeled by
>
> > tornado, but as soon as it goes to django the whole advantage of
>
> > tornado is is not used?
>
> > Am I missing something?
>
> > RTG
>

> > On 7 Dez., 11:16, "Thom Simmons" &amp;lt;t...@sliceofpi.com> wrote:
>
> > > I would say that, simply put, tornado is faster server than the alternatives &amp;amp;amp; wrapping django in tornado is quite easy.

>
> > > I am migrating my production servers to this stack because the perfornance is that good. I am also looking into building a django-native interface to tornado.
>
> > > I'll put together more info soon.
>
> > > Thom Simmons
> > > Slice of Pi, LLC
> > > CTO/Lead Developer
> > > -- Sent from my Palm Prērtg wrote:
>
> > > Hi Thom,
>
> > > what is the main advantage to use nginx+tornado+django as a stack?
>
> > > Thx, RTG
>

> > > On 6 Dez., 13:19, Thom Simmons &amp;amp;lt;t...@sliceofpi.com> wrote:
>
> > > > It depends on your particular setup. If you use something like the
> > > > supervisord-based configuration [found here:http://www.jeremybowers.com/blog/4/tornado-web-framework-production-d...]
> > > > then you would start/restart supervisord to manage the tornado
> > > > processes.
>