|
|
7 ani în urmă | |
|---|---|---|
| .. | ||
| src | 7 ani în urmă | |
| README.md | 7 ani în urmă | |
| benchmark_config.json | 7 ani în urmă | |
| pom.xml | 7 ani în urmă | |
| spring-webflux-mongo.dockerfile | 7 ani în urmă | |
| spring-webflux-postgres.dockerfile | 7 ani în urmă | |
| spring-webflux.dockerfile | 7 ani în urmă | |
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 (postgresql database accesses) to not block netty's event loop.
For postgresql access, JdbcTemplate is used. For mongoDB access, spring-data-mongodb with reactive support is used.
http://localhost:8080/plaintext
http://localhost:8080/json
http://localhost:8080/db
http://localhost:8080/mongo/db
http://localhost:8080/queries?queries=5
http://localhost:8080/mongo/queries?queries=5
http://localhost:8080/updates?queries=5
http://localhost:8080/mongo/updates?queries=5
http://localhost:8080/fortunes
http://localhost:8080/mongo/fortunes