We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
nng
re: #1706 (comment)
i've forked the nng repo under monome and noted what appear to be the relevant vars in nng/CMakeLists.txt
nng/CMakeLists.txt
set(NNG_MAX_TASKQ_THREADS 16 CACHE STRING "Upper bound on taskq threads, 0 for no limit")
set(NNG_MAX_EXPIRE_THREADS 8 CACHE STRING "Upper bound on expire threads, 0 for no limit")
my wonderings:
cmake
waf
third-party
norns-image
also mostly out of curiousity: is having excess nng threads a significant / blocking issue? seems like if idle they wouldn't have too much impact
The text was updated successfully, but these errors were encountered:
No branches or pull requests
re:
#1706 (comment)
i've forked the
nng
repo under monome and noted what appear to be the relevant vars innng/CMakeLists.txt
set(NNG_MAX_TASKQ_THREADS 16 CACHE STRING "Upper bound on taskq threads, 0 for no limit")
set(NNG_MAX_EXPIRE_THREADS 8 CACHE STRING "Upper bound on expire threads, 0 for no limit")
my wonderings:
cmake
build fromwaf
if we submodulenng
underthird-party
? if not then i guess this might better be moved tonorns-image
also mostly out of curiousity: is having excess nng threads a significant / blocking issue? seems like if idle they wouldn't have too much impact
The text was updated successfully, but these errors were encountered: