I think API-Hour uses connection pool for PostgreSQL, right? DB connection has relatively high cost. Especially, PostgreSQL is known that connection cost is higher than MySQL.
In the case of Django, CONN_MAX_AGE configure option enables reuse connections. In the case of Flask, I usually uses SQLAlchemy's engine for connection pooling. On Thu, Mar 12, 2015 at 6:43 AM, Ludovic Gasc <[email protected]> wrote: > Hi people, > > As promised, this is the benchmarks based on your remarks: > http://blog.gmludo.eu/2015/03/benchmark-python-web-production-stack.html > I've started to receive positive feedbacks from few users who use API-Hour > on production, it seems we aren't alone to observe a positive performance > improvements with this architecture. > > Thanks for your constructive remarks. > > Regards. -- INADA Naoki <[email protected]>
