Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*: add fio tests for disk performance #3203

Merged
merged 8 commits into from
Jul 31, 2024

Conversation

KaloyanTanev
Copy link
Contributor

@KaloyanTanev KaloyanTanev commented Jul 30, 2024

  • Change the existing disk write test to use fio
  • Add disk write IOPS test, disk read speed test, disk read IOPS test
  • Update Dockerfile to include fio

category: feature
ticket: #3207

@KaloyanTanev KaloyanTanev self-assigned this Jul 30, 2024
Copy link

codecov bot commented Jul 30, 2024

Codecov Report

Attention: Patch coverage is 6.28571% with 164 lines in your changes missing coverage. Please review.

Project coverage is 57.66%. Comparing base (9755f0a) to head (08cd96e).
Report is 3 commits behind head on main.

Files Patch % Lines
cmd/testperformance.go 6.32% 163 Missing ⚠️
cmd/test.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3203      +/-   ##
==========================================
- Coverage   58.07%   57.66%   -0.41%     
==========================================
  Files         211      211              
  Lines       30253    30369     +116     
==========================================
- Hits        17569    17512      -57     
- Misses      10789    10971     +182     
+ Partials     1895     1886       -9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@KaloyanTanev
Copy link
Contributor Author

Sonarcloud code duplication does not pass, but I personally do not agree with it...

Copy link
Collaborator

@gsora gsora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some comments, I have doubts about the test parameters.

That said, I think we should concentrate disk tests around a block size that makes sense for validator nodes, considering blobs etc.

I'd love @OisinKyne input on this.

cmd/testperformance.go Outdated Show resolved Hide resolved
cmd/testperformance.go Outdated Show resolved Hide resolved
cmd/testperformance.go Outdated Show resolved Hide resolved
cmd/testperformance.go Outdated Show resolved Hide resolved
Copy link
Collaborator

@gsora gsora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some comments, I have doubts about the test parameters.

That said, I think we should concentrate disk tests around a block size that makes sense for validator nodes, considering blobs etc.

I'd love @OisinKyne input on this.

Copy link

sonarcloud bot commented Jul 31, 2024

Quality Gate Failed Quality Gate failed

Failed conditions
50.4% Duplication on New Code (required ≤ 30%)

See analysis details on SonarCloud

@KaloyanTanev KaloyanTanev added the merge when ready Indicates bulldozer bot may merge when all checks pass label Jul 31, 2024
@obol-bulldozer obol-bulldozer bot merged commit d5a59fa into main Jul 31, 2024
11 of 12 checks passed
@obol-bulldozer obol-bulldozer bot deleted the kalo/test-disk-performance-fio branch July 31, 2024 14:19
@@ -47,7 +47,7 @@ func newTestCmd(cmds ...*cobra.Command) *cobra.Command {
root := &cobra.Command{
Use: "test",
Short: "Test subcommands provide test suite to evaluate current cluster setup",
Long: `Test subcommands provide test suite to evaluate current cluster setup. Currently there is support for peer connection tests, beacon node and validator API.`,
Long: `Test subcommands provide test suite to evaluate current cluster setup. The full validator stack can be tested - charon peers, consensus layer, validator client, MEV. Current machine's performance can be examined as well.`,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Long: `Test subcommands provide test suite to evaluate current cluster setup. The full validator stack can be tested - charon peers, consensus layer, validator client, MEV. Current machine's performance can be examined as well.`,
Long: `Test subcommands provide a test suite to evaluate a proposed cluster setup. Aspects such as charon's peer connections, its consensus client, its validator client, candidate MEV relays, the node's disk, memory, and network, and more can all be tested ahead of creating a Distributed Validator.`,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge when ready Indicates bulldozer bot may merge when all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants