[openstack-dev] Standardizing on a WSGI framework [was Re: Pecan vs Falcon?]

Doug Hellmann doug.hellmann at dreamhost.com
Tue Apr 23 16:31:44 UTC 2013

On Tue, Apr 23, 2013 at 8:02 AM, Kurt Griffiths <
kurt.griffiths at rackspace.com> wrote:

> > Why don't we get this into Oslo and at least make an attempt at driving
> the car in the same direction?
> I'm not sure that putting either into Oslo is the right solution, but
> add-ons/hooks that seem to be pretty common would be OK.
> > However, the existing WSGI code in our projects isn't going away any
> > time soon and continues to evolve. I think there'd be huge value in
> > someone incrementally consolidating those WSGI implementations, bit by
> > bit.
> As I mentioned at the summit, we ended up doing Falcon because Pecan and
> Flask were too slow for a chatty data API. That being said, Pecan does
> some nice things for you, and is probably fast enough for management APIs.
> If we could standardize on a couple frameworks, that may be Good Enough .

There are probably some features of "stock" pecan that could be turned off
in a situation where the service is only providing an API. Templating, in
particular, comes to mind. Did you do any profiling to find the areas that
were causing slowdowns, or just the higher-level benchmarks?


> @kgriffs
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130423/3dd3b929/attachment.html>

More information about the OpenStack-dev mailing list