jringuette
17a9dff05d
- Add a new benchmark for spring-webflux using pgclient to asynchronously access the database. (#4111)
|
6 years ago | |
|---|---|---|
| .. | ||
| src | 6 years ago | |
| README.md | 6 years ago | |
| benchmark_config.json | 6 years ago | |
| pom.xml | 6 years ago | |
| spring-webflux-jdbc.dockerfile | 6 years ago | |
| spring-webflux-mongo.dockerfile | 6 years ago | |
| spring-webflux-pgclient.dockerfile | 6 years ago | |
| spring-webflux.dockerfile | 7 years ago | |
README.md
Spring Webflux Benchmarking Test
This is the Spring Webflux portion of a benchmarking test suite comparing a variety of web development platforms.
Netty is used for the async web server, with nearly everything configured with default settings. The only thing changed is Hikari can use up to (2 * cores count) connections (the default is 10). See About-Pool-Sizing
A fixed thread pool of size equals to the number of database connections is used to run all the blocking code (jdbc database accesses) to not block netty's event loop.
For postgresql access, there are two implementations.
- JdbcDbRepository is using JdbcTemplate.
- PgClientDbRepository is using reactive-pg-client For mongoDB access, spring-data-mongodb with reactive support is used. See MongoDbRepository
Plaintext Test
JSON Serialization Test
Database Query Test
Database Queries Test
Database Update Test
Template rendering Test
Versions
Test URLs
Plaintext Test
http://localhost:8080/plaintext
JSON Encoding Test
http://localhost:8080/json
Database Query Test
http://localhost:8080/db
Database Queries Test
http://localhost:8080/queries?queries=5
Database Update Test
http://localhost:8080/updates?queries=5
Template rendering Test
http://localhost:8080/fortunes