Anton Kirilov
1b068fbd24
H2O: Switch the build system to Ninja (#6319)
|
4 년 전 | |
|---|---|---|
| .. | ||
| src | 4 년 전 | |
| template | 9 년 전 | |
| CMakeLists.txt | 6 년 전 | |
| README.md | 4 년 전 | |
| benchmark_config.json | 6 년 전 | |
| config.toml | 4 년 전 | |
| h2o.dockerfile | 4 년 전 | |
| h2o.sh | 4 년 전 | |
README.md
h2o
This is a framework implementation using the H2O HTTP server. It builds directly on top of libh2o instead of running the standalone server.
Requirements
CMake, H2O, libpq, mustache-c, OpenSSL, YAJL
Test implementations
The test implementations are located into the src/handlers directory.
Performance tuning
If the test environment changes, it will probably be necessary to tune some of the framework settings in order to achieve the best performance possible. The most significant parameter is the maximum number of database connections per thread, which is controlled by the DB_CONN variable in the h2o.sh script.
Performance issues
Database tests
libpq does not support command pipelining, and implementing anything equivalent on top of it conflicts with the requirements.
Database updates
In the Citrine environment the database connection settings that improve the performance on the updates test make the other database results worse, and vice versa.
Plaintext
libh2o performs at least one system call per pipelined response.
Contact
Anton Kirilov [email protected]