Skip to content

Conversation

@deivid-rodriguez
Copy link
Contributor

What was the end-user or developer problem that led to this PR?

The currently hardcoded 25 is too much and seems to cause some systems to even run out of memory.

What is your fix for the problem, implemented in this PR?

I chose the use the number of available processors here rather than an arbitrary hardcoded number.

I would expect this to fix #4666 and fix #4353.

It also removes the only rubinius specific code in the repository. We don't really support rubinius so it doesn't make sense to keep those different code branches.

Make sure the following tasks are checked

The currently hardcoded 25 is too much and seems to cause some systems
to even run out of memory.

This also removes the only rubinius specific code in the repository. We
don't really support rubinius so it doesn't make sense to keep those
different branches.
@deivid-rodriguez deivid-rodriguez merged commit 54adf80 into master Jun 14, 2021
@deivid-rodriguez deivid-rodriguez deleted the 25_threads_is_too_much branch June 14, 2021 08:06
deivid-rodriguez added a commit that referenced this pull request Jun 21, 2021
Use a more limited number of threads when fetching in parallel from the Compact Index API

(cherry picked from commit 54adf80)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Possible memory leak, need help diagnosing the issue ThreadError can't create Thread: Resource temporarily unavailable

3 participants