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 config option to set threads for saving images #412

Merged
merged 1 commit into from
Aug 13, 2018

Conversation

mariovisic
Copy link
Contributor

In testing i've found that using around 1.5 times the CPU cores
available on a machine yields the best performance with saving images.

This is really important on machines with a lot of cores, we use 32 core
machines in our tests and using up all the cores cuts down wraith time
in half.

8 seems like a good default, this PR adds the ability to change the
value.

In testing i've found that using around 1.5 times the CPU cores
available on a machine yields the best performance with saving images.

This is really important on machines with a lot of cores, we use 32 core
machines in our tests and using up all the cores cuts down wraith time
in half.

8 seems like a good default, this PR adds the ability to change the
value.
@johnsyweb
Copy link
Contributor

👍

@JimBledsoe
Copy link

I have been using this on my local branch and it has added a tremendous amount of flexibility in testing. I am currently favoring closer to 2x the # cores, but 1.5 is good as well.

@bigmartyn bigmartyn merged commit 0fcd526 into bbc:master Aug 13, 2018
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.

4 participants