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

switch to multiprocessing.dummy to avoid unnecessary separate processes #20

Closed
ryran opened this Issue Nov 3, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@ryran
Owner

ryran commented Nov 3, 2016

Turns out multiprocessing.dummy works just as well and uses threads instead of separate processes! Sweet! Guess I'll be changing the cmdline opt back to --threads.

@ryran ryran added the enhancement label Nov 3, 2016

@ryran ryran self-assigned this Nov 3, 2016

ryran added a commit that referenced this issue Nov 3, 2016

@ryran

This comment has been minimized.

Show comment
Hide comment
@ryran

ryran Nov 3, 2016

Owner

Yay! Done.

$ rhsecapi --help | grep -A1 -- --threads
  -t, --threads THREDS  Set number of concurrent worker threads to allow when
                        making CVE queries (default on this system: 5)
Owner

ryran commented Nov 3, 2016

Yay! Done.

$ rhsecapi --help | grep -A1 -- --threads
  -t, --threads THREDS  Set number of concurrent worker threads to allow when
                        making CVE queries (default on this system: 5)

@ryran ryran closed this Nov 3, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment