[WIP]Update benchmark to support in our TKGM#3
Open
luwang-vmware wants to merge 1 commit intomasterfrom
Open
Conversation
luwang-vmware
force-pushed
the
benchmark_tkgm
branch
2 times, most recently
from
09aebf2 to
f15bcee
Compare
luwang-vmware
changed the title
luwang-vmware
force-pushed
the
master
branch
from
3403f6b to
21b3387
Compare
1. update perfdash as module, then could be imported to benchmark tool 2. add gcs related params and support retrieve test run metric from user specfied gcs 3. support svcCreationLatency comparison
luwang-vmware
force-pushed
the
benchmark_tkgm
branch
from
27855f9 to
f0fb54d
Compare
luwang-vmware
force-pushed
the
master
branch
from
3c192ec to
85a23e2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
specfied gcs
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: