|
|
|
|
|
|
by james_roberts
1650 days ago
|
|
|
In theory, any framework that follows the WSGI guidelines should be able to run on top of FastWSGI and take advantage of its speed. There are many frameworks out there. I do intend to test out some more. For now I've only tested the popular Flask framework and a simple bare bones WSGI app. Flask was never developed to be lightning fast. Even still, I am quite surprised at how slow it is now that I've seen what kind of numbers can be achieved. I haven't looked deep into it to see where the issues might be. As for security, that is a work in progress... I definitely wouldn't use FastWSGI in production in the projects current state. It's still early days in terms of development. |
|
|
https://www.slideshare.net/kwatch/how-to-make-the-fastest-ro...
which lead me to this code.
https://github.com/kwatch/router-sample/blob/master/minikeig...
and i was going to consider trying to benchmark different routers. I started a repo here which drops flask and uses some random router off pypi... https://github.com/byteface/fastwsgitest/blob/master/app.py
and i think i just need to merge that state machine router into it for a test. I believe it's part of the architecture for templating engine called tenjin that predates even jinja?
found your benchmark repo but not installed wrk yet to test.