abastardi
1ba2e5373a
Update web2py tests to production quality (#2263)
|
9 years ago | |
|---|---|---|
| .. | ||
| app | 9 years ago | |
| .gitignore | 9 years ago | |
| README.md | 9 years ago | |
| benchmark_config.json | 9 years ago | |
| compile_apps.py | 9 years ago | |
| gunicorn_conf.py | 9 years ago | |
| requirements.txt | 9 years ago | |
| setup.sh | 9 years ago | |
README.md
web2py Benchmarking Test
This is the web2py portion of a benchmarking tests suite comparing a variety of web development platforms.
The information below is specific to web2py. For further guidance, review the documentation. Also note that there is additional information provided in the Python README.
There are two sets of web2py tests, "web2py-standard" (the default) and "web2py-optimized". The former set is implemented via standard web2py production code. The latter involves several special optimizations that would not be typical of a web2py application but could be implemented in cases were performance is critical.
Web Server and Database Client Software
Test Paths
"web2py-standard" and "web2py-optimized" tests are accessed via the "/standard" and "/optimized" paths, respectively.
- JSON Serialization: "/standard/json", "/optimized/json"
- Single Database Query: "/standard/db", "/optimized/db"
- Multiple Database Queries: "/standard/dbs?queries=#", "/optimized/dbs?queries=#"*
- Fortunes: "/standard/fortunes", "/optimized/fortunes"
- Database Updates: "/standard/update?queries=#", "/optimized/update?queries=#"*
- Plaintext: "/standard/plaintext", "/optimized/plaintext"
*Replace # with an actual number.