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.

Sign up for GitHub

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

Jump to bottom

Allow user to aggressively use memory #164

Merged
merged 4 commits into from
May 20, 2024
Merged

Allow user to aggressively use memory #164

merged 4 commits into from
May 20, 2024

Conversation

dachengx
Copy link
Collaborator

@dachengx dachengx commented May 20, 2024 •
edited
Loading

If you set export AGGRESSIVE_MEMORY_ALLOCATION=1 or whatever other value you will bypass the memory allocation default setting recommended by appletree.

@dachengx dachengx requested a review from zihaoxu98 May 20, 2024 21:06
@coveralls
Copy link

coveralls commented May 20, 2024 •
edited
Loading

Pull Request Test Coverage Report for Build 9166122601

Details

  • 22 of 29 (75.86%) changed or added relevant lines in 3 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.4%) to 85.651%
Changes Missing Coverage Covered Lines Changed/Added Lines %
appletree/utils.py 1 3 33.33%
appletree/likelihood.py 14 19 73.68%
Totals Coverage Status
Change from base Build 9165970399: 0.4%
Covered Lines: 2334
Relevant Lines: 2725
💛 - Coveralls

@dachengx dachengx merged commit c711e74 into master May 20, 2024
7 checks passed
@dachengx dachengx deleted the aggressive_memory_usage branch May 20, 2024 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@zihaoxu98 zihaoxu98 Awaiting requested review from zihaoxu98

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@dachengx @coveralls