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

[ADD] Option to specify number of data points #70

Merged
merged 4 commits into from
Feb 5, 2024
Merged

Conversation

f-dangel
Copy link
Owner

@f-dangel f-dangel commented Feb 4, 2024

At the moment, the number of data points is inferred by a pass through the data loader.
This can become a bottleneck on compute clusters when multiple jobs access the same data set in parallel (experience from a recent ICML submission on the Vector cluster).
To resolve this, the PR adds an optional argument num_data to all non-experimental linear operators which allows to avoid the data set traversal.

@f-dangel f-dangel requested a review from runame February 4, 2024 16:27
@coveralls
Copy link

coveralls commented Feb 4, 2024

Pull Request Test Coverage Report for Build 7787246371

  • 0 of 6 (100.0%) changed or added relevant lines in 4 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 88.454%

Totals Coverage Status
Change from base Build 7787240841: 0.0%
Covered Lines: 858
Relevant Lines: 970

💛 - Coveralls

Copy link
Collaborator

@runame runame left a comment

Choose a reason for hiding this comment

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

black check is currently failing, but besides that, LGTM!

@f-dangel f-dangel merged commit 8bae5de into main Feb 5, 2024
7 checks passed
@f-dangel f-dangel deleted the specify-num-data branch February 5, 2024 16:19
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.

3 participants