search

stackabletech / issues

This repository is only for issues that concern multiple repositories or don't fit into any specific repository
2 stars 0 forks source link

Performance Test #181

Open lfrancke opened 2 years ago

lfrancke commented 2 years ago

Overview

As an administrator/user of our platform I want to make sure that we're not blocked by the Kubernetes networking infrastructure and I want to have a recommendation on which CNI plugin to use.

This epic will be used to track progress of the entire performance test endeavor. At this time, sub-issues just for the planning stage have been added, as activities progress, we will add further subtickets here to track.

We want to define a set of tests that we can run repeatedly on different infrastructures, to evaluate, how much of a difference the management/network/virtualization layer of Kubernetes actually makes for these workloads.

Planning up until now has happened in this document: https://docs.google.com/document/d/1c2ZKf5W9oQn2rvGjRrAzZDEuvQFd-Y6mHqusLn1p07Y/edit#

@garloff and @berendt have expressed an interest in participating in this test as well.

I have extracted parts of this document into issues to allow tracking progress on the board.

This ticket is done when we have a plan (in forms of other tickets/documents, follow up meetings etc.) on how to run a performance test against Kubernetes that tests various CNI plugins against each other. We'd like to find the "ceiling" in terms of network performance.

The actual product used to run those tests is not too important. Coordinate with the SCS folks if needed.

Please add any followup tickets to the same epic.

soenkeliebau commented 2 years ago

@lfrancke I don't want to accept my own refinement

lfrancke commented 2 years ago

Can you make a tasklist out of the items and do you think all of those things can be done in parallel or do they need to be done one after the other?

lfrancke commented 2 years ago

Thank you. You've marked this as an epic. Do you think it makes sense to then rename this Epic to just "Performance Test" and have the plan as its first step? Alternatively we could create a parent epic and this as a subepic but our tooling is not really set up for that yet.

soenkeliebau commented 2 years ago

I have added "depends on #..." to the sub-issues where appropriate.

For https://github.com/stackabletech/issues/issues/278 one could argue that it depends on https://github.com/stackabletech/issues/issues/277 because otherwise no metric list can be defined - but we might also just accept "gather all jmx metrics that are available" as acceptable..

Do you think it makes sense to then rename this Epic to just "Performance Test" and have the plan as its first step? Alternatively we could create a parent epic and this as a subepic but our tooling is not really set up for that yet.

I have no strong opinion.

lfrancke commented 2 years ago

In that case I do: Let's make this Epic about the whole Performance Test. I think we just need to add a sentence or two about that at the top and then later continue adding subtasks when we have made a plan.

soenkeliebau commented 2 years ago

In that case I do: Let's make this Epic about the whole Performance Test. I think we just need to add a sentence or two about that at the top and then later continue adding subtasks when we have made a plan.

done