Opened 4 years ago
Last modified 4 years ago
#2188 closed enhancement
nginx -t with many worker_processes/reuseport is expensive — at Version 1
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | documentation | Version: | 1.18.x |
| Keywords: | Cc: | ||
| uname -a: | Linux laptop 5.10.0-1-amd64 #1 SMP Debian 5.10.4-1 (2020-12-31) x86_64 GNU/Linux | ||
| nginx -V: | not relevant | ||
Description (last modified by )
nginx -t forks worker_processes worker processes just like normal nginx. With reuseport in listen directive in use each of the workers create separate socket. On modern multicore machine (assuming i.e. worker_processes auto;) this creates a lot of sockets which are not of much value. Large configurations take a lot longer to test.
I think we could assume in testing that configuration has worker_processes 1;. Is this problematic in any way?
We can't use -g option to override configured value, because nginx complains about duplicated directive.
Note:
See TracTickets
for help on using tickets.
