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

Support multiple releases on graphs #489

Merged
merged 2 commits into from
Oct 24, 2024

Conversation

soyacz
Copy link
Collaborator

@soyacz soyacz commented Oct 23, 2024

Performance job can run against different scylla release. Because it was
not taken into account, graph lines don't differentiate between them
making impossible to distinguish different releases.

This commit adds support for mixing different SUT releases in one job
and make them visible as separate series on graphs. Additional
'releases' filters were added to easily toggle releases that should be
shown.

closes: #473

Removing leftover from debugging.
@soyacz soyacz requested review from fruch and k0machi October 23, 2024 14:15
@soyacz
Copy link
Collaborator Author

soyacz commented Oct 23, 2024

It's not visible that good as I have randomized test data. Note the graph legend on each graph, also there's point shape difference between releases. I left colors the same, but I'm not sure, maybe we should change hue or something to additionally differentiate.
Without filters:
image

With filter on:
image

Copy link
Collaborator

@k0machi k0machi left a comment

Choose a reason for hiding this comment

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

Overall looks good, I do have some questions about frontend presentation - see comment about charts. One thing as well - looking at some of the graphs in production I can also see that uneven grid sometimes making it hard to read - is that a side effect of trying to line up the dates? Couldn't we set it up in a way that makes the grid uniform (don't have to have legend for each x value)?

argus/backend/service/results_service.py Outdated Show resolved Hide resolved
argus/backend/service/results_service.py Show resolved Hide resolved
argus/backend/service/results_service.py Show resolved Hide resolved
argus/backend/service/results_service.py Show resolved Hide resolved
Copy link
Collaborator

@k0machi k0machi left a comment

Choose a reason for hiding this comment

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

Also should probably look into making a nicer color scheme - should probably avoid 255 for anything, check bootstrap main color scheme that we use for something more easy on the eyes.

@soyacz soyacz self-assigned this Oct 24, 2024
@soyacz soyacz force-pushed the support-multiple-releases-on-graphs branch from 5f71bf9 to 37bc485 Compare October 24, 2024 09:56
Performance job can run against different scylla release. Because it was
not taken into account, graph lines don't differentiate between them
making impossible to distinguish different releases.

This commit adds support for mixing different SUT releases in one job
and make them visible as separate series on graphs. Additional
'releases' filters were added to easily toggle releases that should be
shown.

closes: scylladb#473
@soyacz soyacz force-pushed the support-multiple-releases-on-graphs branch from 37bc485 to 8bd2cc6 Compare October 24, 2024 11:12
@soyacz soyacz merged commit 8a97b18 into scylladb:master Oct 24, 2024
1 check passed
@soyacz
Copy link
Collaborator Author

soyacz commented Oct 24, 2024

@fruch after adjusting to @k0machi feedback and testing it on staging, we decided to merge it - if you have more feedback, let me know.

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

Successfully merging this pull request may close these issues.

Filter graphs data by release
2 participants