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

[TASK] Create a performance and scalability report against 1.2.0 #2811

Closed
1 task
innobead opened this issue Jul 19, 2021 · 4 comments
Closed
1 task

[TASK] Create a performance and scalability report against 1.2.0 #2811

innobead opened this issue Jul 19, 2021 · 4 comments
Labels
area/performance System, volume performance duplicated kind/task General task request to fulfill another primary request priority/1 Highly recommended to fix in this release (managed by PO) require/doc Require updating the longhorn.io documentation
Milestone

Comments

@innobead
Copy link
Member

innobead commented Jul 19, 2021

What's the task? Please describe.

We did a report for 1.0 (https://longhorn.io/blog/performance-scalability-report-aug-2020/), but it was quite a long time ago before 1.1 and 1.2 releases. During this period, we have some improvements like replica rebuilding, legacy harddisks via timeout changes, etc, so we would like to see the updated report to reflect the current status.

Describe the items of the task (DoD, definition of done) you'd like.

  • As per the same testing architecture, create the report in terms of IOPS, latency and throughput

Additional context

We also need to consider the reporting automated after the report is created. (cc @meldafrawi )

cc @longhorn/qa

@innobead innobead added require/doc Require updating the longhorn.io documentation kind/task General task request to fulfill another primary request area/performance System, volume performance labels Jul 19, 2021
@innobead innobead added this to the v1.2.0 milestone Jul 19, 2021
@innobead innobead added this to To do in QA/DevOps Tasks via automation Jul 19, 2021
@yasker
Copy link
Member

yasker commented Jul 19, 2021

FYI: I've started a new benchmark project at https://github.com/yasker/benchmark, with the intention of moving it to Longhorn later. I haven't got much time to work on it yet. In general, we should depreciate https://github.com/longhorn/dbench/ and containerize https://github.com/yasker/benchmark to provide a generalized benchmark framework for Kubernetes workloads. The goal is to replace dbench with longhorn/benchmark as the de-facto standard benchmark for Kubernetes storage.

At least it should be:

  1. Able to deploy via Kubernetes
  2. Able to test raw block storage as well as a file system (on top of block device or not, thinking NFS).

@yasker
Copy link
Member

yasker commented Jul 21, 2021

OK, the new benchmark tool is up at https://github.com/longhorn/benchmark .

@innobead innobead added the priority/1 Highly recommended to fix in this release (managed by PO) label Aug 2, 2021
@innobead
Copy link
Member Author

We can do this after 1.2.0 out.

@innobead innobead modified the milestones: v1.2.0, v1.2.1 Sep 7, 2021
@innobead
Copy link
Member Author

innobead commented Sep 8, 2021

Closing because of a duplicated #2986

@innobead innobead closed this as completed Sep 8, 2021
QA/DevOps Tasks automation moved this from To do to Done Sep 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/performance System, volume performance duplicated kind/task General task request to fulfill another primary request priority/1 Highly recommended to fix in this release (managed by PO) require/doc Require updating the longhorn.io documentation
Projects
No open projects
Development

No branches or pull requests

3 participants