Anton Kirilov 1b068fbd24 H2O: Switch the build system to Ninja (#6319) пре 4 година
..
src 1b068fbd24 H2O: Switch the build system to Ninja (#6319) пре 4 година
template 29ef2fd38e H2O: Add implementation пре 9 година
CMakeLists.txt a8432f24e8 H2O: Further code clean-up (#4680) пре 6 година
README.md 1b068fbd24 H2O: Switch the build system to Ninja (#6319) пре 4 година
benchmark_config.json f5e7fff93e Config now show the webserver h2o (#4864) пре 6 година
config.toml 9d18b6e21b make sure all have versus key (#6265) пре 4 година
h2o.dockerfile 1b068fbd24 H2O: Switch the build system to Ninja (#6319) пре 4 година
h2o.sh 1b068fbd24 H2O: Switch the build system to Ninja (#6319) пре 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]