-
Notifications
You must be signed in to change notification settings - Fork 715
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
CustomWaterfall: add min functionality #3057
CustomWaterfall: add min functionality #3057
Conversation
Tagging @mjkozicki , @claud-io , would appreciate if you could review this PR and provide feedback. |
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.
LGTM.
Minimum
time feels a bit off and Start
seems more appropriate but given that the end is called Maximum
it is appropriate to keep it aligned.
Thanks for doing this, it's been a long-standing request and I've been dreading going through the scaling code. The change looks nice and clean.
@mjkozicki ...PING... Can you review (and merge if things look good)? |
@mjkozicki @claud-io ...PING, PING... Can you review (and merge if things look good)? |
Hello @jspurlin we are testing it, will let you know once is done. Thanks |
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.
@jspurlin seems page sometimes break when min >= max or with neg numbers, can you please add check for those cases? thanks
@jspurlin thanks, going to start testing it |
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.
Handle the case where max is not provided. Also make sure not to show page_events < min_ms
@lbartoli79 Done. I've made sure to account for the case where min is provided but max is not and not to draw vertical lines < min_ms |
...PING... @claud-io and @lbartoli79 |
Prior to this PR users could only set a max time to filter on when creating custom waterfalls. This meant that custom waterfalls always started at t=0 even if what you cared about didn't start until the t=5s mark
This PR adds the ability to optionally specify a min time to filter on in addition to setting a max and requests to filter on.
I verified that the custom filter scales correctly in app parts (Requests, CUP Utilization, Bandwidth, Browser Main Thread, and Long Tasks)
For example, if I care about the 5-10s range of the waterfall this is what it looks like
Before
After
This is a fix for Add ability to specify min/start time for custom waterfalls #3042