Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ayqVo-0006iq-2k for pgsql-hackers@arkaria.postgresql.org; Sat, 07 May 2016 00:54:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ayqVn-0002kD-KR for pgsql-hackers@arkaria.postgresql.org; Sat, 07 May 2016 00:54:27 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ayqVm-0002jT-Bo for pgsql-hackers@postgresql.org; Sat, 07 May 2016 00:54:26 +0000 Received: from mail-wm0-x22e.google.com ([2a00:1450:400c:c09::22e]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ayqVj-0008CK-6t for pgsql-hackers@postgresql.org; Sat, 07 May 2016 00:54:24 +0000 Received: by mail-wm0-x22e.google.com with SMTP id n129so75512762wmn.1 for ; Fri, 06 May 2016 17:54:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=n+oJcpzNEpLcH1A3wWaNRV7EQmdxA2scK98UcOm5ZmI=; b=uaIq+gWA9zEcolhBRoNJBKVlBXE16WupCJh7KEdaB3EIuer/Xgv4lUwEY/Hx9V6en4 N8ic+Bv1JDm/7iIls+ey3GZRsNu7O/zCbnkW9W67RpI/jTd5oZKmseHg44qKA/6wGp1y DUjJ3GJNG2qj6FMsyQDVlZLrI1N98W0D0fITOhFku02Q/43LKIEK+/JTZMzIVN6DQcne reFN863NcFPhAgpxRayIdAZB7cI5pdXnd2fyTsn21I9PdE/0KzpVKNzJToyeRM7xStXE DiiJyeN1ywVepm7nuFr4trWNRw3MogXUhCqewCcnCDX47Z/VzaB89F5pEbWdLWgbj8Td mEdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=n+oJcpzNEpLcH1A3wWaNRV7EQmdxA2scK98UcOm5ZmI=; b=ijOARfh0KGqHTa7U/aU7r/51H15iW3wCnOyWunfi6bf2FZ0e0r+Dt49vHt/jWjAiin cYFGKRLZYJ+XHRuOhDlUSLlRW7cVId36E0BwCK7UsKTjJUMARDGgsT3uxa2ftuCiwr3C G9khSnMlAPL67rkJw+q8m/jcQCPaEe6YTuJms23FtgK3D/C/c19IcjD+uutm26cISfJt poagVzQ0DLbNtSnaSe8kfkH8+pxaLZ+jcXHq1Ly2mB99hikrhczOufMgD2mwNvZ4CoTU OWgXj/CVUTbuuCv0ZARtjmaZZC71MncCZT1sMMa6yV6wQwQpucG2LUo199ru50Jz+6d7 kAyQ== X-Gm-Message-State: AOPr4FVImqeiur2fVufl5FZx8LqAtBCY7bUfpdVSKO7ozkkMHO6HqIFWpxMJHUCyVHnvoXEawzLpG65Pj7Q0miOfyPckVPvKMwSCFRkLZ306wMS4JagUzk2oAHlFMdCt3MyYvDkYzkzpuwzUEMT/rt3XpeU3aBucp4b3D8bnG+nBoVymOUiD5Da1EJMfVjwZWQ9JYujLwnxU X-Received: by 10.28.85.3 with SMTP id j3mr52294wmb.0.1462582461036; Fri, 06 May 2016 17:54:21 -0700 (PDT) Received: from [10.137.2.20] (ip-89-177-44-58.net.upcbroadband.cz. [89.177.44.58]) by smtp.gmail.com with ESMTPSA id m14sm10964442wmc.4.2016.05.06.17.54.19 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 May 2016 17:54:20 -0700 (PDT) Subject: Re: what to revert To: Andres Freund References: <20160503162209.ufuezlkovbrdrayp@alap3.anarazel.de> <20160503174104.tk7oz4akwbeqsmuq@alap3.anarazel.de> <20160503224241.rwtxrhgmprzqxhlv@alap3.anarazel.de> Cc: pgsql-hackers@postgresql.org From: Tomas Vondra Message-ID: Date: Sat, 7 May 2016 02:54:18 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Thunderbird/46.0a2 MIME-Version: 1.0 In-Reply-To: <20160503224241.rwtxrhgmprzqxhlv@alap3.anarazel.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Hi, On 05/04/2016 12:42 AM, Andres Freund wrote: > On 2016-05-03 20:57:13 +0200, Tomas Vondra wrote: >> On 05/03/2016 07:41 PM, Andres Freund wrote: ... >>> I'm pretty sure that I said that somewhere else at least once: But to >>> be absolutely clear, I'm *not* really concerned with the performance >>> with the feature turned off. I'm concerned about the performance with >>> it turned on. >> >> If you tell me how to best test it, I do have a 4-socket server sitting idly >> in the corner (well, a corner reachable by SSH). I can get us some numbers, >> but I haven't been following the snapshot_too_old so I'll need some guidance >> on what to test. > > I think it'd be cool if you could test the effect of the feature in > read-only (and additionally read-mostly?) workload with various client > counts and snapshot_too_old values. For the latter maybe -1, 0, 10, 60 > or such? I've done so (accidentally comparing 0 and 1 instead of -1 and > 1) on a two socket machine in: > www.postgresql.org/message-id/20160413171955.i53me46fqqhdlztq@alap3.anarazel.de > > It'd be very interesting to see how big the penalty is on a bigger box. OK. I do have results from mater with different values for the GUC (-1, 0, 10, 60), but I'm struggling with the reverts. Can you provide a patch against current master (commit 4bbc1a7e) that does the revert? regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers