Project

General

Profile

Actions

Bug #20594

closed

scaling nginx settings

Added by Peter Amstutz about 1 year ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Target version:
Story points:
-
Release relationship:
Auto

Description

The values of worker_rlimit_nofile and worker_connections need to scale with CONTROLLER_MAX_CONCURRENT_REQUESTS instead of being hardcoded, and they need to be at least 2x as large as the concurrent requests, because each request handler will have a client request and a database connection.


Subtasks 1 (0 open1 closed)

Task #20596: Review 20594-scaling-nginx-settingsResolvedPeter Amstutz05/26/2023Actions
Actions #1

Updated by Peter Amstutz about 1 year ago

  • Status changed from New to In Progress
Actions #2

Updated by Peter Amstutz about 1 year ago

  • Description updated (diff)
Actions #3

Updated by Peter Amstutz about 1 year ago

  • Category set to Deployment
Actions #4

Updated by Peter Amstutz about 1 year ago

  • Assigned To set to Lucas Di Pentima
  • Status changed from In Progress to New
Actions #5

Updated by Lucas Di Pentima about 1 year ago

  • Status changed from New to In Progress
Actions #6

Updated by Lucas Di Pentima about 1 year ago

Updates at b859429 - branch 20594-scaling-nginx-settings

Makes nginx's config settings 3x the CONTROLLER_MAX_CONCURRENT_REQUESTS value, if set.

Validated it by testing on the scale cluster.

Actions #7

Updated by Peter Amstutz about 1 year ago

Lucas Di Pentima wrote in #note-6:

Updates at b859429 - branch 20594-scaling-nginx-settings

Makes nginx's config settings 3x the CONTROLLER_MAX_CONCURRENT_REQUESTS value, if set.

Validated it by testing on the scale cluster.

This LGTM, thank you

Actions #8

Updated by Lucas Di Pentima about 1 year ago

  • Status changed from In Progress to Resolved
Actions #9

Updated by Peter Amstutz 10 months ago

  • Release set to 66
Actions

Also available in: Atom PDF