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

adding an atime test case Performance Regression with .N and := #PR5463 #6169

Closed
wants to merge 5 commits into from

Conversation

DorisAmoakohene
Copy link
Contributor

This atime test case discusses the issue of [Performance Regression with .N and := (https://github.com/https://github.com/https://github.com//issues/5424)

The cause of the regression is related to the addition of the snprintf function in the assign.c. #4491

The Regression was fixed by creating targetDesc function and adding snprintf in assign.c Fixes Regression

Copy link

github-actions bot commented Jun 4, 2024

Comparison Plot

Generated via commit 515415e

Download link for the artifact containing the test results: ↓ atime-results.zip

Time taken to finish the standard R installation steps: 11 minutes and 13 seconds

Time taken to run atime::atime_pkg on the tests: 4 minutes and 1 seconds

dt <- data.table(
id = seq_len(N),
val = rnorm(N))
dt
Copy link
Member

Choose a reason for hiding this comment

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

please remove line with dt by itself which does nothing but is potentially confusing

Copy link
Contributor Author

Choose a reason for hiding this comment

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

alright

@tdhock
Copy link
Member

tdhock commented Jun 6, 2024

great thanks

@tdhock
Copy link
Member

tdhock commented Jun 6, 2024

please add your name to DESCRIPTION as a contributor

val = rnorm(N))
},
expr = data.table:::`[.data.table`(dt, , .(vs = (sum(val))), by = .(id)),
Before = "be2f72e6f5c90622fe72e1c315ca05769a9dc854", # Parent of the regression causing commit (https://github.com/Rdatatable/data.table/commit/e793f53466d99f86e70fc2611b708ae8c601a451) in the PR that introduced the issue (https://github.com/Rdatatable/data.table/pull/4491/commits)
Copy link
Member

Choose a reason for hiding this comment

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

please use comment templates https://github.com/Rdatatable/data.table/wiki/Performance-testing#documentation-of-historical-commits
If this commit is in the PR then use
Parent of the commit which caused the regression in the PR (PR_LINK)"

otherwise use Parent of first commit (COMMIT_LINK) in the PR (PR_LINK) which causes the issue

Before = "be2f72e6f5c90622fe72e1c315ca05769a9dc854", # Parent of the regression causing commit (https://github.com/Rdatatable/data.table/commit/e793f53466d99f86e70fc2611b708ae8c601a451) in the PR that introduced the issue (https://github.com/Rdatatable/data.table/pull/4491/commits)
Regression = "e793f53466d99f86e70fc2611b708ae8c601a451", # Commit responsible for regression in the PR that introduced the issue (https://github.com/Rdatatable/data.table/pull/4491/commits)
Fixed = "58409197426ced4714af842650b0cc3b9e2cb842") # Last commit in the PR that fixed the regression (https://github.com/Rdatatable/data.table/pull/5463/commits)
Before = "fda7fd9dbcac939df33769193eebd44731ee59b9", # Parent of the regression commit (https://github.com/Rdatatable/data.table/commit/c4a2085e35689a108d67dacb2f8261e4964d7e12)
Copy link
Member

Choose a reason for hiding this comment

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

parent of this Regression commit (c4a2085) is not appropriate here, because this Regression commit is the parent of the first commit in the fix PR (not the commit which caused the regression), so the parent of this Regression commit could still be slow.

If the previous Regression commit (e793f53) is the commit which caused the regression, then it would be appropriate to use its parent as Before.

Please revert this commit, and write proper documentation comments for the commit IDs you were using before.

@tdhock
Copy link
Member

tdhock commented Jul 18, 2024

closing since we already have a performance test for the issue which was fixed in #5463

@tdhock tdhock closed this Jul 18, 2024
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.

None yet

3 participants