Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJe3t-0061nr-WE for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Jun 2024 19:00:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sJe3r-000x3w-5d for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Jun 2024 19:00:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJe3q-000x3P-RN for pgsql-hackers@lists.postgresql.org; Tue, 18 Jun 2024 19:00:07 +0000 Received: from mail-io1-xd2f.google.com ([2607:f8b0:4864:20::d2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sJe3p-002KWK-3H for pgsql-hackers@postgresql.org; Tue, 18 Jun 2024 19:00:07 +0000 Received: by mail-io1-xd2f.google.com with SMTP id ca18e2360f4ac-7eb9e7f3da2so244400939f.1 for ; Tue, 18 Jun 2024 12:00:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718737203; x=1719342003; darn=postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=2C+tULhTdbAWT7yZJNXo6ahlFwB8yBDITIgVlMhfQbE=; b=bnp3SkQknaHWvzzDMhE6sGx+B5IgV8q5e2sTFQg+Btqt/WAlTXNGt6P88psYtjSVAo L7L1dyzY9mRlxqKE3IpvG3+pFecA4ZWQJ6sqw4Gg2JbrsiRMVyztoRuuYYWSEdUNYJhm udC93XA/oTIMe+7vxNTvjS5Dcl1NgO9igUyaI2dnKIIVAsmyBkMS1Sp2UlxHRU2jWudO Gtp2vsaRCS7+6ieo2yc0NLha2plU7ueD/BpUaih5LdEaC6YfjSAUGqhZVfxDQJkSYdn2 mZhR5l9r9+oEggWeowS+Kllj/OF3Ks50R2ePsmmRiJJNGdV62dxmRe/SigXqd4y+dIlo 6eDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718737203; x=1719342003; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=2C+tULhTdbAWT7yZJNXo6ahlFwB8yBDITIgVlMhfQbE=; b=xR2H4oxQmwxoU25c8+m68XDoOCBIJkOockM4STZ2f4lKZAFmG+OzJhOFTLr1qQ3IeS uRLQIjnCTqOBiizHYj6wT0rUOvRVi2NG0+Fv+g9+N67ZD6AZUiduJrengz5ZlTiEHKrT xlBqwxqGN2lyuR3RTBPugY5x4Q3bPK4deV5/7UedjcJfVmIrfw8eadSyGEqcWZQLRFKc 4RIRE8jnKHgMzLuby6w3ANiXo32LlwQnlB0LYxxbPBIqLFGgaexTHNXn4vLWKooRCqvw VeQiKnzfxbR3B3LKnAoczvszmpw3gIbaqRsHeGY1e5aqdpvicGSgbxx9XqAGui/lf1BH NXZA== X-Forwarded-Encrypted: i=1; AJvYcCXE5wbJ2Xh+dNJZyz6TG6v8PQKIIVCdH2hSN35m3xU5J1mXq0VLdRcWmGO8kiTeFa0M+LomA6tTJHAOmH3mVK499K6ASOAu5SMBHgp9 X-Gm-Message-State: AOJu0YzRKUR4Qx/RJ0MPQeAEu0gCQEJ1GIimURN8oz0/NIdEEwzKbTKn QIf4gzbZo01pEYureDP93vYSlvl62IlDnQAByXZL4+DlPxiCtuu9 X-Google-Smtp-Source: AGHT+IEnfVMEPw8m+k7DXwGBLzhu2a9rPpJj1gkg8mE2NgMOHFPH1Xkwifc3skYyoBoyuiPZn6aZhQ== X-Received: by 2002:a05:6e02:1847:b0:376:1808:f8b1 with SMTP id e9e14a558f8ab-3761d76e120mr6296635ab.30.1718737202793; Tue, 18 Jun 2024 12:00:02 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id e9e14a558f8ab-375d86bde71sm22548595ab.38.2024.06.18.12.00.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 18 Jun 2024 12:00:02 -0700 (PDT) Date: Tue, 18 Jun 2024 14:00:00 -0500 From: Nathan Bossart To: Andres Freund Cc: "Imseih (AWS), Sami" , Justin Pryzby , "pgsql-hackers@postgresql.org" Subject: Re: allow changing autovacuum_max_workers without restarting Message-ID: References: <96B4FC7B-A919-4F93-80A3-BA3EA4F8479A@amazon.com> <20240503010415.GA1008894@nathanxps13> <2780DB08-DCA6-4E57-B823-303A0E7E17D7@amazon.com> <20240507160605.GA2523153@nathanxps13> <011CA929-4933-40EA-B1D3-29131FEFBCF0@amazon.com> <20240517021646.GA1745636@nathanxps13> <20240603190852.jcibstxflb33hjvu@awork3.anarazel.de> <20240603232427.pjiyqggsr7duccr5@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240603232427.pjiyqggsr7duccr5@awork3.anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Jun 03, 2024 at 04:24:27PM -0700, Andres Freund wrote: > On 2024-06-03 14:28:13 -0500, Nathan Bossart wrote: >> On Mon, Jun 03, 2024 at 12:08:52PM -0700, Andres Freund wrote: >> > Why do we think that increasing the number of PGPROC slots, heavyweight locks >> > etc by 256 isn't going to cause issues? That's not an insubstantial amount of >> > memory to dedicate to something that will practically never be used. >> >> I personally have not observed problems with these kinds of bumps in >> resource usage, although I may be biased towards larger systems where it >> doesn't matter as much. > > IME it matters *more* on larger systems. Or at least used to, I haven't > experimented with this in quite a while. > > It's possible that we improved a bunch of things sufficiently for this to not > matter anymore. I'm curious if there is something specific you would look into to verify this. IIUC one concern is the lock table not fitting into L3. Is there anything else? Any particular workloads you have in mind? -- nathan