Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
From: Andriy Kornatskyy <andriy.kornatskyy@live.com>
To: <demianbrecht@gmail.com>
Subject: RE: Fastest web framework
Date: Tue, 16 Oct 2012 19:35:39 +0300
Importance: Normal
In-Reply-To: <507D8632.7040804@gmail.com>
References: <DUB117-W80EE2285B5E415AA14B5B9919F0@phx.gbl>, <mailman.2203.1350308439.27098.python-list@python.org>, <8b51748d-0517-4b1d-a0a6-e8fa06dd4b68@r10g2000pbd.googlegroups.com>, <DUB117-W741B72171E7BBFB4B07D7791700@phx.gbl>, <CAE+T62Z7mbRcuhnWJcYQCL5SOQDQou8o6SSR7Hkx+KRj8eyBEg@mail.gmail.com> <DUB117-W27EF5EE49EA42A6CE186E791700@phx.gbl>, <507D8632.7040804@gmail.com>
Content-Type: text/plain; charset="windows-1251"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "python-list@python.org" <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.2290.1350405408.27098.python-list@python.org>
Lines: 70
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:31417


Demian=2C

Thank you=2C see below.

> I think that my first batch of questions were slightly out of context=2C
> mostly due to a lack of caffeine first thing in the morning. My
> understanding at the time was that your "an answer to effectivity" was=2C
> in fact=2C a list of highlights for wheezy.web (which is why I asked the
> questions I did). Having said that..
>
> > The initial decisions taken while building a project might be wrong.
> Due to continues backward compatibility=2C you can not change them even
> you wish.
>
> You can always deprecate old functionality in favor of new solutions.
> I'd be hard pressed to find a reason to find a reason why something
> *can't* be deprecated. It may not be easy at times=2C but it should alway=
s
> be doable.

And that is the problem. Some can not deprecate and die (see pylons=2C now =
pyramid). Some can not die nor deprecate (see django).

> > That glue is usability case: recommendation how to use it with one or
> the other.
>
> As long as your framework doesn't require you to fight with it in order
> to use another solution. One of my early gripes with Django for example
> (ages ago) was that it felt like I had to fight the framework in order
> to introduce functionality that wasn't natively supported.
>
> > For you=2C personally=2C let me point this again. N.P.
> >
> > Here is how: use content caching with cache dependency. Read more:
> > http://packages.python.org/wheezy.http/userguide.html#content-cache
>
> It doesn't matter if you're using cached content or not. It will *not*
> be as fast as a hard-coded=2C simple response (not that a static=2C
> hard-coded response is the way to go obviously). I don't think I have to
> get into the details about I/O. My point is simply that the statement
> that a database driven site (cached content or not)=2C *can not* be as
> fast as a "hello world" app. My comment may be construed as being
> nit-picky=2C but I thought it was worth calling out due to the
> matter-of-fact wording that you used.

It does. There is certain level after which performance of `hello world` wi=
ll not differ from real world application. The hardware I used got that lim=
it at 22-24K per second. That is why I made isolated benchmarks. See differ=
ence between wsgi sample and others.

http://mindref.blogspot.com/2012/09/python-fastest-web-framework.html

> On a somewhat unrelated note=2C I caught a minor typo in the content-cach=
e
> docs:
>
> "Since there is no heavy processing and just simple operation to get an
> item from cache it should be supper fast"
>
> I don't know about you=2C but my supper generally isn't fast =3B)

You will see. Thanks. supper =3D> super =3B-)

Somewhat later in a week there will be another benchmark for... caching.

Take care.

Andriy
 		 	   		  =