Anton Kirilov a2f3f1011e H2O: Optimize the database updates test further (#8570) 1 year ago
..
src a2f3f1011e H2O: Optimize the database updates test further (#8570) 1 year ago
template 29ef2fd38e H2O: Add implementation 9 years ago
CMakeLists.txt ee07fd2481 Update H2O to version 2.3.0 (#8069) 2 years ago
README.md bee2f94e8b H2O: Clean up the Dockerfile (#8009) 2 years ago
benchmark_config.json 8638739872 H2O: Update the base image to Ubuntu 22.04 (#7375) 3 years ago
config.toml 9d18b6e21b make sure all have versus key (#6265) 4 years ago
h2o.dockerfile a2f3f1011e H2O: Optimize the database updates test further (#8570) 1 year ago

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 -m and the -e command-line options respectively.

Performance issues

Plaintext

libh2o performs at least one system call per pipelined response.

Contact

Anton Kirilov [email protected]