Michael Bromley 5654a6e046 chore: Publish v0.15.1		5 vuotta sitten
..
load-testing	beab829b6b chore(dev-server): Update load-test config	5 vuotta sitten
test-plugins	a4f716fba9 chore(dev-server): Clean up example plugins	5 vuotta sitten
.gitignore	e3c9bb6752 chore: Add link to load test doc, increase order limit for load tests	6 vuotta sitten
README.md	e3c9bb6752 chore: Add link to load test doc, increase order limit for load tests	6 vuotta sitten
dev-config.ts	1a37148fb7 refactor(admin-ui): Support modified config op def API	5 vuotta sitten
docker-compose.yml	2ccf9d5663 chore(dev-server): Add MySQL to docker-compose	5 vuotta sitten
file-logger.ts	8d49af31d9 chore(dev-server): Create SimpleFileLogger	6 vuotta sitten
index-worker.ts	c1ccaa1e83 feat(core): Validate DB table structure on worker bootstrap	5 vuotta sitten
index.ts	c1ccaa1e83 feat(core): Validate DB table structure on worker bootstrap	5 vuotta sitten
migration.ts	d509805f58 feat(core): Export database migration helpers	6 vuotta sitten
package.json	5654a6e046 chore: Publish v0.15.1	5 vuotta sitten
populate-dev-server.ts	ac1006489c refactor(core): Move cli dir to top level	5 vuotta sitten
tsconfig.json	e24b33e677 fix: Enable noImplicitAny on core and fix all tsc errors	6 vuotta sitten

Vendure Dev Server

This package is not published to npm. It is used in development of the Vendure server and plugins.

Running

To run the server, run the start script. The database configuration can be specified by the DB=<type> environment variable:

DB=mysql yarn start
DB=postgres yarn start
DB=sqlite yarn start

The default if no db is specified is mysql.

Populating data

Test data can be populated by running the populate script. This uses the same sample data as is used by the Vendure CLI when running init, albeit with the additional step of populating some sample customer & address data too.

Specify the database as above to populate that database:

DB=sqlite yarn populate

Load testing

This package also contains scripts for load testing the Vendure server. The load testing infrastructure and scripts are located in the ./load-testing directory.

Load testing is done with k6, and to run them you will need k6 installed and (in Windows) available in your PATH environment variable so that it can be run with the command k6.

The load tests assume the existence of the following tables in the MySQL database:

vendure-load-testing-1000
vendure-load-testing-10000
vendure-load-testing-100000

The npm scripts load-test:1k, load-test:10k and load-test:100k will populate their respective databases with test data and then run the k6 scripts against them.

Running individual scripts

An individual test script may be by specifying the script name as an argument:

yarn load-test:1k deep-query.js

Results

The results of the test are saved to the ./load-testing/results directory. Each test run creates two files:

load-test-<date>-<product-count>.json Contains a summary of all load tests run
load-test-<date>-<product-count>-<script-name>.csv Contains time-series data which can be used to create charts

Historical benchmark results with charts can be found in this Google Sheet