Butterfly Bones
Very Senior Member
That was explained by kvic in the pixelserv-tls thread back in the earlier active days of development. That is by design when you get say 15-20 people all web browsing and all those ads hitting so pixelserv-tls increases the number requests per service thread and then the number of active service threads. When / if activity slows, the number of service threads will decrease.I too have seen, and regularly do see my pixelserv-tls thread count go up over 100, and the memory grows too. Then it stops and works it way down to 2 or 3 threads. No idea what is causing this yet.
It all shows in the pixelserv stats.
Code:
pixelserv-tls 2.3.1 (compiled: Jan 31 2020 13:27:14 flags: tfo tls1_3) options: 192.168.1.2
uts 0d 00:44 process uptime
log 1 critical (0) error (1) warning (2) notice (3) info (4) debug (5)
kcc 1 number of active service threads
kmx 1 maximum number of service threads
kvg 0.00 average number of requests per service thread
krq 0 max number of requests by one service thread