Nate 8d10136e89 remove $CPU_COUNT (#3474) 7 ani în urmă
..
aiohttp dc59e82b3f use latest aiohttp release (#3421) 7 ani în urmă
api_hour 14fed64a25 Docker python (#3406) 7 ani în urmă
apistar 14fed64a25 Docker python (#3406) 7 ani în urmă
bottle 8d10136e89 remove $CPU_COUNT (#3474) 7 ani în urmă
cherrypy 14fed64a25 Docker python (#3406) 7 ani în urmă
django 14fed64a25 Docker python (#3406) 7 ani în urmă
falcon 14fed64a25 Docker python (#3406) 7 ani în urmă
flask 8d10136e89 remove $CPU_COUNT (#3474) 7 ani în urmă
japronto c01fe61374 Docker python (#3410) 7 ani în urmă
klein c01fe61374 Docker python (#3410) 7 ani în urmă
morepath c01fe61374 Docker python (#3410) 7 ani în urmă
pyramid c01fe61374 Docker python (#3410) 7 ani în urmă
sanic c01fe61374 Docker python (#3410) 7 ani în urmă
tornado 51035538bc tornado update (#3463) 7 ani în urmă
turbogears c01fe61374 Docker python (#3410) 7 ani în urmă
uvicorn c01fe61374 Docker python (#3410) 7 ani în urmă
uwsgi 8d10136e89 remove $CPU_COUNT (#3474) 7 ani în urmă
web2py 22b26e76ee Docker Remaining Python Tests (#3415) 7 ani în urmă
webware 97ba6b2f91 Docker lua (#3436) 7 ani în urmă
weppy 8d10136e89 remove $CPU_COUNT (#3474) 7 ani în urmă
wheezyweb 22b26e76ee Docker Remaining Python Tests (#3415) 7 ani în urmă
wsgi 22b26e76ee Docker Remaining Python Tests (#3415) 7 ani în urmă
README.md 882490524e Upgrade Python 3 + PyPy => PyPy2 rename + PyPy3 integration (#2918) 8 ani în urmă

README.md

Python frameworks

The information below contains information specific to Python. For further guidance, review the documentation.

Infrastructure Software Versions

Get Help

Python Experts

  • INADA Naoki (@methane) -- CPython core developer and expert of Python's MySQL driver.
  • Ludovic Gasc (@GMLudo) -- AsyncIO and aiohttp user.

Python Community

Python interpreters

(C)Python 3

Newest Python.

It is the most major interpreter for Web Development.

(C)Python 2

Legacy Python. Still used for widely.

PyPy3

PyPy is the fastest Python implementation with JIT.

PyPy2

Legacy PyPy. Still used for widely.

WSGI Servers

Nginx + uWSGI

This is one of fast and realistic way to serve Python web application.

Use unix domain socket between nginx and uWSGI to avoid additional TCP/IP overhead.

Gunicorn + Meinheld

Meinheld is very fast WSGI server.

Since Meinheld is safe against slowloris and support Keep-Alive, you can use it without buffered HTTP reverse proxy (like nginx).

We use meinheld to measure bare (without DB access) performance of framework without overhead of reverse proxying. (plaintext, json test)

Meinheld does not provide worker process management. Gunicorn provide it for Meinheld.

Gunicorn + Tornado

uWSGI + PyPy is difficult to setup. Meinheld doesn't so fast with PyPy because it uses Python/C API heavily. So we use Tornado as HTTP/WSGI server.

It supports keep-alive. So it have nice performance about json or plaintext benchmark.

Before writing new tests.

Don't increase matrix without significant purpose.

We can't maintain matrix of frameworks (5~) * servers (3~) * DBs (3) * Interpreters (3).

If you want to know about performance difference between MySQL and PostgreSQL, there are no need to all frameworks implement both of them.

Additionally, Python is not a good language to measure performance of DBs because web application written in Python is slower than DBs.

If you want to benchmark http server, you should not port all tests or frameworks. Simple json or plaintext test is enough.

If your framework uses SQLAlchemy, Flask may be enough to know performance of SQLAlchemy.

Advice when writing new tests

Interpreter

Consider Python 3 first. -- Python 3 is mainstream for web development.

Server

Try Gunicorn + Meinheld first. All WSGI apps in this benchmark uses it. You can compare your framework performance with others.

Files you should provide

You can see Flask's files to know how to write new test.

requirements.txt is standard way to define depending libraries.

install.sh is executed before running test. You should create virtualenv on $TROOT/py2 (or py3 for Python 3 and pypy for PyPy). Then $TROOT/py2/bin/pip install -r requirements.txt. virtualenv is installed on Python 2 and PyPy. Use $IROOT/py3/bin/python3 -m venv $TROOT/py3 for Python 3.

You can set environment variables within install.sh or within setup.sh.

bechmark_config is json file to define test. See here.

setup_py2.sh is used to run test on Python 2. gunicorn_conf.py is configuration for gunicorn. setup_py2.sh and gunicorn_conf.py are written as generic as possible. You may be able to use it with changing wsgi callable. ($PY2_GUNICORN wsgimodule:callable -c gunicorn_conf.py)