Sorry for spamming.
Investigated a bit of correct `assumedDescriptorsPerRequest` value. Looks like
it requires a single file description to handle a single request (tested by
simple curl call). But this does not take into account the fact, that idle
processes consume some amount of file descriptors.
For me (mac os) it was `9`:
lsof -a -p 31299
COMMAND PID USER FD TYPE DEVICE SIZE/OFF
NODE NAME
server 31299 romka cwd DIR 1,4 128
22182574 /Users/romka/t/nim-server-error
server 31299 romka txt REG 1,4 527336
22190701 /Users/romka/t/nim-server-error/server
server 31299 romka txt REG 1,4 2547760
1152921500312767057 /usr/lib/dyld
server 31299 romka 0u CHR 16,0 0t5236958
3121 /dev/ttys000
server 31299 romka 1u CHR 16,0 0t5236958
3121 /dev/ttys000
server 31299 romka 2u CHR 16,0 0t5236958
3121 /dev/ttys000
server 31299 romka 3u IPv4 0x50c0746d84061b8d 0t0
TCP *:cslistener (LISTEN)
server 31299 romka 4u KQUEUE
count=0, state=0xa
server 31299 romka 5u IPv4 0x50c0746d84061165 0t0
TCP *:* (CLOSED)
Run
I'm not sure, why `6` works for `assumedDescriptorsPerRequest`, possible not
all lines in the output of `lsof` are real file descriptors, but looks like a
good strategy for setting `assumedDescriptorsPerRequest` will be a prior
investigation of idle process needs and then setting safe value. The value will
be different depending on dozen of factors, i.e. connections to DB, logging to
files, etc.
