Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mLUYe-0001Ys-T2 for pgsql-novice@arkaria.postgresql.org; Wed, 01 Sep 2021 18:01:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mLUYc-0002FY-GN for pgsql-novice@arkaria.postgresql.org; Wed, 01 Sep 2021 18:01:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mLUYc-0002DH-5X for pgsql-novice@lists.postgresql.org; Wed, 01 Sep 2021 18:01:54 +0000 Received: from mail-wm1-x331.google.com ([2a00:1450:4864:20::331]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mLUYZ-0003yh-FO for pgsql-novice@lists.postgresql.org; Wed, 01 Sep 2021 18:01:53 +0000 Received: by mail-wm1-x331.google.com with SMTP id 79-20020a1c0452000000b002e6cf79e572so291454wme.1 for ; Wed, 01 Sep 2021 11:01:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=r7Nf0abaD5amMNR9Ear0zGzQqL08U68D2ul3NoscxAg=; b=q+KmwsvNm5GiZOSvG2pbZGa+v+v88EOxzl2yLabZHRGtfcro75r/voodKdgE0Lzijw bOFzhJuixVkpnaX8xjzjUsSOyAkRrah87aYJh7Q06HcpTLaiU8wQ2hBzqjmvW4Ad7Lkx dPsJgsLfW3lIekjun5/VT2nWKjDIt6+eVid4WJ8v64ElrO62DY5jxijFG9PcBFfU8nGD 2nncLRAJzstHGy2px2zidXheZO3NDnhT4Vi9EHU+LIjdqh0+LyCK2C5Um6SziZCl8hvi sDXCKXCHQOHWcUIexpuxMZiSaJWS6Wb/rDt/HhjiUrJZOZMHs60malYetDYKwI1WapLr zdsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=r7Nf0abaD5amMNR9Ear0zGzQqL08U68D2ul3NoscxAg=; b=XVft19Cm1g+GTAdLb3aDFTlDb+7BrMatSfSr5yp45HlCu3YBUZRkC4BuzWGIic7X81 QdJOnVrTGQxpqmgMqDBbdFSbcdxJfg2g9626Bj0fntD2/hBbcX1DQdh00WdD6Mzi/Xcx sFbWsadXPINYTn+dHC4iGF3QFhsjaJ7+lzxlIQSXfm6mrePsh/aDUGlKahPkRPph0IIq Z5DPBqxkl6SPsSHLAQwcohKAihrsJaxUjwTmdU/u+otURXHlZwEhN8lUn5+HT4pmYqwx IMJiNzeVTd1dhc91O3RF8Rz+j9SOHmCB1u0Cuks6N8xTPxqwGjOP9bWp+skWi1nHr+dU xRsQ== X-Gm-Message-State: AOAM530kElepOAtXC1+19yxHUzTzAokQAgC88zt4dbLaSvlBwaBFeIJO WmU7mOcFzcfbdGeYKnZnUTlNeqJ3F5sgrg== X-Google-Smtp-Source: ABdhPJxEPKMntz5EZyLYHYsVuSRWb13BzwYboqqOodgR/Qb3F18QVCXe9sq+meWvlfFUfiAKDthywg== X-Received: by 2002:a1c:7403:: with SMTP id p3mr792628wmc.72.1630519309368; Wed, 01 Sep 2021 11:01:49 -0700 (PDT) Received: from localhost.localdomain (dynamic-e2z1otx8d37jftanm-pd01.res.v6.highway.a1.net. [2001:871:5c:b592:69f5:1301:a2a0:a632]) by smtp.gmail.com with ESMTPSA id r25sm182945wra.12.2021.09.01.11.01.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 01 Sep 2021 11:01:48 -0700 (PDT) Message-ID: <7d31e25d6cdd46ab94559179268e61413849d741.camel@cybertec.at> Subject: Re: Using PGTune - is it a good source for system configuration? From: Laurenz Albe To: =?ISO-8859-1?Q?P=F3l?= Ua =?ISO-8859-1?Q?Lao=EDnech=E1in?= , pgsql-novice@lists.postgresql.org Date: Wed, 01 Sep 2021 20:01:48 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-1.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2021-09-01 at 17:19 +0100, Pól Ua Laoínecháin wrote: > I used PGTune to obtain system configuration recommendations. I'm > wondering if these can be taken as "gospel" or are there any caveats > or "gotchas" to be aware of? It is a serving suggestion and gives you food for thought. It does not substitute thinking for yourself and reading the documentation for those parameters. > # DB Version: 13 > # OS Type: linux > # DB Type: mixed > # Total Memory (RAM): 32 GB > # CPUs num: 2 > # Data Storage: ssd > > max_parallel_workers_per_gather = 1 > max_parallel_workers = 2 > max_parallel_maintenance_workers = 1 For example, I think these are not sane values for a mixed workload with 2 CPU cores. With that configuration, a single query could keep both cores busy. I'd set all these to 0. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com