Thanks for the advice, but I already know how to optimize django apps
(documentation covers this well), so I'm not seeking advice on this.
Neither I'm willing to use Cherokee so I get a magic performance boost
for my app alone (while it is indeed faster than Apache for serving
static content).

Instead, I'm looking for advice from someone who already deployed
Django with Cherokee.

On Oct 7, 2:41 am, Graham Dumpleton <graham.dumple...@gmail.com>
wrote:
> On Oct 7, 3:34 pm, hcarvalhoalves <hcarvalhoal...@gmail.com> wrote:
>
>
>
> > I recently found this web server (http://www.cherokee-project.com/)
> > that claims to be "the fastest web server". I'm not sure that holds
> > true for *CGI, but at least for static content they have some
> > impressive benchmarks. Despite the claimings, it's an interesting
> > alternative for what it supports out-of-the-box alone: administrative
> > interface, simpler configuration, transparent restart, load balancer,
> > db balancer, virtual hosts, TLS, and some other cool, easy to setup
> > features.
>
> > Setting it up for working with Django is a breeze (http://www.cherokee-
> > project.com/doc/cookbook_django.html) and I already did some tests,
> > now I'm considering trying it in production.
>
> > I wanted to know if someone here on the list is using or used Cherokee
> > with Django, if there's any performance improvements over Apache +
> > mod_wsgi/mod_python (specially for concurrent requests), and if there
> > are any gotchas with Django 1.1.
>
> Repeat after me 100 times. The bottleneck is not the web server, it is
> your application logic, use of caching and the database.
>
> Chase the mythical fastest web server in the world, of which there are
> many to choose from based on claims they all make, but you will be
> wasting your time. If you want better performance, you are better off
> focusing on addressing the performance problems your own application
> and the database introduces.
>
> So, just use whatever web server you have a tendency to like, that you
> find easy to configure and maintain, and which you perceive as being
> stable. After all, you don't want to have to tangle with the web
> server, you will need all the time you have to make your own
> application work better.
>
> Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to