Anton Kirilov
b0146dfab6
H2O: Reduce the number of system calls executed for database access (#7918)
|
2 rokov pred | |
|---|---|---|
| .. | ||
| src | 2 rokov pred | |
| template | 9 rokov pred | |
| CMakeLists.txt | 3 rokov pred | |
| README.md | 2 rokov pred | |
| benchmark_config.json | 3 rokov pred | |
| config.toml | 4 rokov pred | |
| h2o.dockerfile | 2 rokov pred | |
| h2o.sh | 2 rokov pred | |
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, numactl, OpenSSL, YAJL
Test implementations
The test implementations are located into the src/handlers directory - refer to
the initialize_*_handler*() functions.
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 parameters are the
maximum number of database connections per thread and the maximum number of pipelined database
queries per database connection, which are controlled by the DB_CONN and the DB_PIPELINE
variables respectively in the h2o.sh script.
Performance issues
Plaintext
libh2o performs at least one system call per pipelined response.
Contact
Anton Kirilov [email protected]