Benchmarks for ASP.NET Core including (but not limited to) scenarios from the TechEmpower Web Framework Benchmarks.
The current results tracked by the ASP.NET team are available at this location.
The benchmarking infrastructure is made of these components:
This will assume you have Docker installed and are familiar with it.
Setup the Benchmark Servercd docker/benchmarks
./build.sh
, which will build a Docker image containing the benchmarking dependencies/etc/environment
DBHOST=10.0.0.103
by replacing the IP with the one used to communicate with the database serverserver_ip=10.0.0.102
by replacing the IP with the one used to communicate with the benchmark serverhardware_version=HPZ440
by replacing with a description of the hardware. This will be used when storing the results to distinguish environments/etc/hosts
and add 10.0.0.103 TFB-database
with the IP to the database server./run-server.sh
The application should start on port 5001
. Open a browser on this page and OK
should be displayed.
cd docker/benchmarks
./build.sh
, which will build a Docker image containing the benchmarking dependencies./run-client.sh
The application should start on port 5002
. Open a browser on this page and OK
should be displayed.
cd docker/postgres-techempower
./build.sh
./run.sh
This will create and run a Docker image containing PostgreSql and the Fortunes database that is used by Tech Empower scenarios.
On your computer,
cd src/BenchmarksDriver
dotnet run -c Debug \
--server "http://10.0.0.102:5001" \
--client "http://10.0.0.101:5002" \
--jobs "../Benchmarks/benchmarks.json.json" \
--scenario Json
This will start the Json
scenario using the Benchmarks
application that is provided in https://github.com/aspnet/benchmarks/tree/master/src/Benchmarks. You can use another application by setting the correct arguments described on this page.
Some of the Benchmarks
application scenarios require the database to be selected from the driver. By default no database driver will be configured and these scenarios will fail. For instance, running the DbFortunesEF
scenario will require the driver to have the --database
argument.
A good default is --database PostgreSql
which will use NpgSql, but other providers are available. See the command line arguments for the available ones.
The driver application can store the results of a job by passing a -q [connectionstring]
argument. The connection string must point to an existing SQL Server database. The first time it's called the required table will be created. From there you can create reports using the tools of your choice.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4