Skip to content

Conversation

@SimonHeybrock
Copy link
Member

Some benchmarks were failing with exit status -9. This might fix it. The benchmarks seemed to be using close to 4 GByte RAM, which gets close to the 7 GByte available on the GitHub hosted runners.

Some benchmarks were failing with exit status -9. This *might* fix it.
The benchmarks seemed to be using close to 4 GByte RAM, which gets close
to the 7 GByte available on the GitHub hosted runners.
Copy link
Member

@jl-wynen jl-wynen left a comment

Choose a reason for hiding this comment

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

It still allocated the full data array. So the question is, is the peak memory consumption in setup or in the timing functions?

Did you run the benchmarks on this branch?

@SimonHeybrock
Copy link
Member Author

Yes I ran it and it reduced the memory consumption.

@SimonHeybrock SimonHeybrock merged commit 58f53c7 into main Nov 7, 2023
@SimonHeybrock SimonHeybrock deleted the reduce-asv-bench-memory-use branch November 7, 2023 08:09
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