That's great news.

Gevent has very high concurency performance, but in my experience there can
be very large standard deviation in latency, so I still think we should
benchmark paste vs paste for most applications (which are going to have
blocking events like database access, etc).

But I expect that all the work you've been doing to optimize the tg2 stack
and python code will make a big difference, even without the gevent foo!

--Mark Ramm

On Wed, Dec 21, 2011 at 4:28 AM, Alessandro Molina <
[email protected]> wrote:

> I still have to look how crank integrates in TG, but it should be
> framework independent it shouldn't be an issue.
>
> As I worked hard at optimizing the pylons-less branch in the last
> week, using profiler middleware and a set of some benchmark testing tg
> applications,  I have been able to push the performances from
> ~800req/sec up to ~1700req/sec on my machine (most simple app without
> templating on gevent,  genshi quickstart app on paste got from 58r/s
> to 77r/s) some of the changes I did apply to the dispatching and so
> should probably be ported to crank in the case we switch to it.
>
> On Wed, Dec 21, 2011 at 5:45 AM, Michael Pedersen <[email protected]>
> wrote:
> > Here's a question to consider in this discussion:
> >
> > Alessandro has put together a branch that removes Pylons as a
> requirement.
> > What happens if we go forward with that branch? How does it affect Crank?
> > Are the two of them compatible, or will we have to make a choice between
> > them?
> >
> >
> > On Thu, Dec 15, 2011 at 5:15 PM, percious <[email protected]> wrote:
> >>
> >> To bring the discussion back to crank, and relate to what Chris said.
> >>
> >> Crank actually allows us to move over to pyramid without maintaining
> >> multiple codebases if we decide to do that.  I realize we are spinning
> off
> >> one of the major parts of TG, but I think in this case it makes sense.
>  This
> >> was a big problem with TG1.0, 1.5 and 2.0, all of which have separate
> >> codebases to maintain for dispatch.
> >>
> >> I agree that TG should remain as a first-class citizen with Crank, and
> >> that backwards compatibility should be maintained.  I have done
> everything
> >> in my power to make sure that the existing 2.1.x tests work with crank
> in
> >> the codebase.
> >>
> >> As a side note, I'm writing something to remove the repoze.w* mess, and
> I
> >> plan on spinning off the part of the code that selects
> templates/template
> >> engines into it's own package, or partnering with Alice of web.core to
> >> utilize alacarte, which is a replacement for buffet.  I'm tired of
> >> maintaining multiple dotted template lookup code too ;-)
> >>
> >> cheers.
> >> -chris
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "TurboGears Trunk" group.
> >> To view this discussion on the web visit
> >> https://groups.google.com/d/msg/turbogears-trunk/-/7F_CCpa9aZgJ.
> >>
> >> To post to this group, send email to [email protected].
> >> To unsubscribe from this group, send email to
> >> [email protected].
> >> For more options, visit this group at
> >> http://groups.google.com/group/turbogears-trunk?hl=en.
> >
> >
> >
> >
> > --
> > Michael J. Pedersen
> > My Online Resume: http://www.icelus.org/ -- Google+
> http://plus.ly/pedersen
> > Google Talk: [email protected] -- Twitter: pedersentg
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "TurboGears Trunk" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected].
> > For more options, visit this group at
> > http://groups.google.com/group/turbogears-trunk?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "TurboGears Trunk" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/turbogears-trunk?hl=en.
>
>


-- 
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog

-- 
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/turbogears-trunk?hl=en.

Reply via email to