-
Notifications
You must be signed in to change notification settings - Fork 82
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
DCOS-51377: Services Table: avoid rerender (except for status icons) #3796
Conversation
legit fails |
a03443f
to
2c22720
Compare
This seems to duplicate #3792 but missing all the service status column stuff? |
@natmegs Because of the accurate service merges there are quite some conflicts for the status column with every PR we merge on that topic. Let's revisit this soon and do a final rebase once the accurate service work is all done 👍 This PR aims to get a good chunk of the progress merged soon. |
2c22720
to
93208d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i opened master and the new branch side by side and behaviour seems to be the same against soak.
on my machine it's rather a ~30% boost instead of the advertised ~50% on scripting.
that's not to disparage these awesome changes! 🎉
EDIT: i looked at the memory consumption and for a single measurement, these changes appear to have increased base consumption while flattening deviation. not tested thoroughly, but i thought this might be worth sharing nonetheless:
(40s each - interestingly you can count 20 bumps on master, while it's hard to see that on this branch)
plugins/services/src/js/containers/services/__tests__/ServicesTableRenderers-test.js
Outdated
Show resolved
Hide resolved
93208d2
to
eeb407d
Compare
I split up the commits to be per column for easier rebasing and I also removed the unit tests, because they did not seem to add any value |
These tests only test if the business logic values from the structs are passed correctly to the components, which is a matter of our integration tests.
Closes DCOS-51377
Closes DCOS-51377
Closes DCOS-51377
Closes DCOS-51377
Closes DCOS-51377
Closes DCOS-51377
Closes DCOS-51377
Closes DCOS-51377
Closes DCOS-51377
eeb407d
to
702400e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some nits one nit, nothing that has to be changed in this PR. one question about tests tho.
@@ -1,190 +0,0 @@ | |||
import { NumberCell } from "@dcos/ui-kit"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
did you ensure we have integration tests testing this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I wrote some of them back then :)
</span> | ||
</div> | ||
</TextCell> | ||
<ServiceName |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'nit: I think it would have been possible to split this into ServiceName
and GroupName
component 🤔 not sure if I'm missing something and I think its not that important tho.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as before, I did not touch anything in this direction. I don't see that this is part of the scope of this ticket.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least if our goal is still to merge this functionality today. If this goal changed we can also close this PR and use the #3792 one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, lets get it in, we can improve later
🎉 This PR is included in version 2.81.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Testing
Trade-offs
Dependencies
Screenshots