Skip to content

Full Range Benchmark Result Chart #1842

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

Merged
merged 3 commits into from
Mar 12, 2024
Merged

Conversation

eth3lbert
Copy link
Contributor

Resolves #1835

@Kobzol
Copy link
Contributor

Kobzol commented Mar 11, 2024

Hi, thanks for the PR! I'm a bit busy at the moment, but I'll try to take a look this week.

@eth3lbert
Copy link
Contributor Author

no worries! take your time :)

@eth3lbert eth3lbert force-pushed the chart-range branch 2 times, most recently from 76de622 to 21d74b5 Compare March 12, 2024 09:14
@eth3lbert
Copy link
Contributor Author

I keep forgetting fmt and check. 😅
Rebased and feedback addressed. Thanks for the review and feedback.

Copy link
Contributor

@Kobzol Kobzol left a comment

Choose a reason for hiding this comment

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

Looks good, thank you! Let's see how it works on production data.

@Kobzol Kobzol merged commit 908eaaf into rust-lang:master Mar 12, 2024
@Kobzol
Copy link
Contributor

Kobzol commented Mar 12, 2024

image

Ah, looks like the end date should be trimmed in the UI. The server caps it at the commit date, but here it is displayed in the future, which doesn't make sense.

@Kobzol
Copy link
Contributor

Kobzol commented Mar 12, 2024

While we're at it, the The shaded region shows values that are more recent than the benchmarked commit message should change benchmarked to end.

@eth3lbert Let me know if you wanna fix these things :) If not, I'll take a look at it.

@eth3lbert
Copy link
Contributor Author

Ah, looks like the end date should be trimmed in the UI. The server caps it at the commit date, but here it is displayed in the future, which doesn't make sense.

To confirm, is the issue related to how the graph title displays the end date? Specifically, you want it to show "today" (or the last date from the response) if it's a future date, is that correct?

@Kobzol
Copy link
Contributor

Kobzol commented Mar 12, 2024

Yeah, it's just about the UI text. The end date can be in the future w.r.t. the benchmarked commit, that is fine, but it should never be in the actual future, w.r.t. "today" :)

@eth3lbert
Copy link
Contributor Author

Ok, I will take a look.

@Zentrik
Copy link
Contributor

Zentrik commented Mar 12, 2024

This is also seemed to break the link to the history graph, start is now a human formatted date which is incorrect, e.g. https://perf.rust-lang.org/index.html?start=Sun%20Feb%2011%202024%2014:01:38%20GMT+0000%20(Greenwich%20Mean%20Time)&end=7de1a1f6db26cf7af43cca74819118428e6317ee&benchmark=exa-0.10.1&profile=opt&scenario=incr-full&stat=instructions:u

To fix just update

const start = getPastDate(new Date(commit.date), 30);
to use fomatDate.

@eth3lbert
Copy link
Contributor Author

This is also seemed to break the link to the history graph, start is now a human formatted date which is incorrect, e.g. https://perf.rust-lang.org/index.html?start=Sun%20Feb%2011%202024%2014:01:38%20GMT+0000%20(Greenwich%20Mean%20Time)&end=7de1a1f6db26cf7af43cca74819118428e6317ee&benchmark=exa-0.10.1&profile=opt&scenario=incr-full&stat=instructions:u

Thanks for letting me know! I'll get it fixed.

@eth3lbert
Copy link
Contributor Author

eth3lbert commented Mar 12, 2024

@Kobzol I guess this could be resolved at the computing graph range function, right? Or is there any reason to allow the end date to be after the current date?

If we address this in the computing graph range, we might want to reintroduce the previous implementation related to daysInPast 😅

@Kobzol
Copy link
Contributor

Kobzol commented Mar 12, 2024

I think that the only thing that should be added is make sure that end is earlier_or(end_commit_date + DAYS_RANGE / 2, today). Also, if the end day is today, then start should be set to today - 30 days (unless the start_commit_date is earlier, of course).

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.

Allow displaying the benchmark result detail chart for the full range
3 participants