Test migration tool with 100 GiB model
Context
This is part of Test offline migration runtime with test registries of different sizes and storage backends epic that aims to perform tests against test registries of different sizes and using different storage backends, starting with GCS, S3, and the local storage filesystem.
Proposed Tests
- | One Step Import | Three Step Import |
---|---|---|
AWS | 8 min. | one: 6 min. 11 sec.; two: 16 sec.; three: 1 min. 26 sec. (~8min.) |
GCP | ~52 min. | one: ~23 min.; two: ~2 min.; three: ~27 min. (52 min.) |
GCP Seeding time: 0 hours, 15 minutes, and 49 seconds to complete.
GCS Bucket Size: 5.13 MiB (Model), Bucket Location: US (multiple regions in US)
GCP GitLab instance region/zone: europe-north1-a
AWS Seeding time: 0 hours, 8 minutes, and 15 seconds to complete.
S3 Bucket Size: 5.3217 MiB (Model), Bucket Location: us-east-1
AWS GitLab instance region/zone: us-east-1
Execution Plan
- Setup 1k Reference Architecture in AWS|GCP using GET
- Use the seeding model defined for 100 GB (Reference | Model) to populate the Container Registry
- Run the migration tool with One Step import
- Post results in the table above
- Repeat steps from 1. for Three Step Import
Cost Analysis
Evaluate the cost of the experiment after execution in AWS and GCP.
Edited by Sofia Vistas