Michael Bromley 2f5e096b27 feat(core): Add bulk delete mutations hace 2 años
..
load-testing f02a463bfc chore: Lint fixes hace 2 años
scripts e196dc3f13 chore: Add test collections script hace 4 años
test-plugins 2f5e096b27 feat(core): Add bulk delete mutations hace 2 años
.gitignore be35b5f195 chore: Enable custom admin ui in dev-server hace 2 años
README.md aed08dd414 chore: Add simple query load test, enable pg stats hace 4 años
dev-config.ts 18c4a16f27 chore(dev-server): Add example ui extension hace 2 años
docker-compose.yml aed08dd414 chore: Add simple query load test, enable pg stats hace 4 años
file-logger.ts 8d49af31d9 chore(dev-server): Create SimpleFileLogger hace 6 años
index-worker.ts 0441a0338a chore: Migrate from TSLint to ESLint hace 2 años
index.ts 0441a0338a chore: Migrate from TSLint to ESLint hace 2 años
memory-profiler.ts 0441a0338a chore: Migrate from TSLint to ESLint hace 2 años
migration.ts d509805f58 feat(core): Export database migration helpers hace 6 años
package.json 30a297e9af chore: Pre-release v2.0.0-beta.2 hace 2 años
populate-dev-server.ts 0441a0338a chore: Migrate from TSLint to ESLint hace 2 años
tsconfig.json e24b33e677 fix: Enable noImplicitAny on core and fix all tsc errors hace 6 años

README.md

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 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

pg_stat_statements

The following queries can be used when running load tests against postgres to analyze the queries:

SELECT 
  dbid,
  (total_time / 1000 / 60) as total, 
  (total_time/calls) as avg, 
  calls,
  query 
FROM pg_stat_statements 
WHERE dbid = <db_id>
ORDER BY total DESC 
LIMIT 100;

-- SELECT pg_stat_statements_reset();

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