diff options
author | Aaron Merey <amerey@redhat.com> | 2022-09-02 21:23:32 -0400 |
---|---|---|
committer | Frank Ch. Eigler <fche@redhat.com> | 2022-09-05 13:17:32 -0400 |
commit | a176b6e30aa8983c95b81f18c34a2b5c6a0c907b (patch) | |
tree | 5fc7f5863b93414534a3f7cb44530ff5dbdec203 /doc/debuginfod.8 | |
parent | 8c68c312699e196d8f9ad14d378762cfd8bc2c94 (diff) | |
download | elfutils-a176b6e30aa8983c95b81f18c34a2b5c6a0c907b.tar.gz |
debuginfod: Use auto-sized connection pool when -C is not given with arg
Since commit 4b42d9ad, libmicrohttpd's epoll event loop is used when
available in which case we must disable its setting for spawning a thread
per request. This contradicts the debuginfod doc's description of '-C',
which indicates that if this command line option is not given then the
thread pool size is unbounded.
Fix this by using an auto-sized thread pool when '-C' is not given, just
as we do when it's given with no argument. Update the doc's description
of '-C'.
Also use a fixed-size pool even if epoll is not supported. The unbounded
pool config cannot be considered entirely reliable as it appears to cause
random fails in the run-debuginfod-webapi-concurrency test.
Signed-off-by: Aaron Merey <amerey@redhat.com>
Diffstat (limited to 'doc/debuginfod.8')
-rw-r--r-- | doc/debuginfod.8 | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/doc/debuginfod.8 b/doc/debuginfod.8 index 50fce7f5..7c1dc3dd 100644 --- a/doc/debuginfod.8 +++ b/doc/debuginfod.8 @@ -212,15 +212,13 @@ following table summarizes the interpretaton of this option and its optional NUM parameter. .TS l l. -no option clone new thread for every request, no fixed pool -\-C use a fixed thread pool sized automatically +no option, \-C use a fixed thread pool sized automatically \-C=NUM use a fixed thread pool sized NUM, minimum 2 .TE -The first mode is useful for friendly bursty traffic. The second mode -is a simple and safe configuration based on the number of processors. -The third mode is suitable for tuned load-limiting configurations -facing unruly traffic. +The first mode is a simple and safe configuration based on the number +of processors. The second mode is suitable for tuned load-limiting +configurations facing unruly traffic. .TP .B "\-L" |