Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
H
hivemind
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
hive
hivemind
Merge requests
!352
Changed methodology for benchmarks
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
Changed methodology for benchmarks
dk-benchmarks-ver-2
into
develop
Overview
0
Commits
3
Pipelines
0
Changes
1
Merged
Dariusz Kędzierski
requested to merge
dk-benchmarks-ver-2
into
develop
4 years ago
Overview
0
Commits
3
Pipelines
0
Changes
1
Expand
Usage of pytest-benchmarks is dropped since it call tests sequentially which very long time to complete, instead original tavern tests are used
Time measuring is done via durations switch to pytest and tavern
During benchmarking validate_response.py is disabled using nevly introduced env variable
Each run creates xml junit file with time data
After all runs data from files are combined and report file is generated
Tests above threshold are marked with red
0
0
Merge request reports
Loading