mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-04 12:02:55 +00:00
8db84d9964
## Problem We have no specific benchmark testing project migration of postgresql project with existing data into Neon. Typical steps of such a project migration are - schema creation in the neon project - initial COPY of relations - creation of indexes and constraints - vacuum analyze ## Summary of changes Add a periodic benchmark running 9 AM UTC every day. In each run: - copy a 200 GiB project that has realistic schema, data, tables, indexes and constraints from another project into - a new Neon project (7 CU fixed) - an existing tenant, (but new branch and new database) that already has 4 TiB of data - use pgcopydb tool to automate all steps and parallelize COPY and index creation - parse pgcopydb output and report performance metrics in Neon performance test database ## Logs This benchmark has been tested first manually and then as part of benchmarking.yml workflow, example run see https://github.com/neondatabase/neon/actions/runs/11757679870
24 lines
550 B
YAML
24 lines
550 B
YAML
self-hosted-runner:
|
|
labels:
|
|
- arm64
|
|
- large
|
|
- large-arm64
|
|
- small
|
|
- small-arm64
|
|
- us-east-2
|
|
config-variables:
|
|
- AZURE_DEV_CLIENT_ID
|
|
- AZURE_DEV_REGISTRY_NAME
|
|
- AZURE_DEV_SUBSCRIPTION_ID
|
|
- AZURE_PROD_CLIENT_ID
|
|
- AZURE_PROD_REGISTRY_NAME
|
|
- AZURE_PROD_SUBSCRIPTION_ID
|
|
- AZURE_TENANT_ID
|
|
- BENCHMARK_PROJECT_ID_PUB
|
|
- BENCHMARK_PROJECT_ID_SUB
|
|
- REMOTE_STORAGE_AZURE_CONTAINER
|
|
- REMOTE_STORAGE_AZURE_REGION
|
|
- SLACK_UPCOMING_RELEASE_CHANNEL_ID
|
|
- DEV_AWS_OIDC_ROLE_ARN
|
|
- BENCHMARK_INGEST_TARGET_PROJECTID
|