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

Restructure naming format in benchmark results #45

Open
darshanasbg opened this issue Oct 10, 2019 · 1 comment
Open

Restructure naming format in benchmark results #45

darshanasbg opened this issue Oct 10, 2019 · 1 comment

Comments

@darshanasbg
Copy link
Contributor

This is regarding: https://github.com/wso2/performance-is/tree/master/benchmarks

Current filenames are as follows.
single-node-2-core-5.8.0-2019-05-14.md
single-node-4-core-5.8.0-2019-05-09.md
single-node-4-core-5.9.0-2019-10-03.md
2-node-cluster-2-core-5.8.0-2019-05-30.md
2-node-cluster-4-core-5.8.0-2019-05-24.md

We should remove the date as it does not effect for the perf result. As we plan to maintain pre-release results (milestones,alpha,beta,rc results) as well as post release results (wum packs) we need to have exact release version of the pack in the filename.

As an external user will be mostly looking for a performance benchmarks for a particular product version, IMO we can have the first identifier as product version number then go to the deployment details. Like,

  • 5.8.0-beta6_single-node_4-core.md
  • 5.8.0-rc2_single-node_2-core.md
  • 5.8.0_two-nodes_2-core.md
  • 5.8.0_two-node_4-core.md
  • 5.9.0_single-node_4-core.md

Need to think on the formatting with the docker based deployments as well.

@aaujayasena
Copy link
Contributor

Add heap size, db instance type, jvm, os parameters when naming the results, if results are with different in mentioned parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants