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 1uDhxK-00EpVZ-VA for pgsql-hackers@arkaria.postgresql.org; Sat, 10 May 2025 11:01:23 +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 1uDhxI-002BNy-92 for pgsql-hackers@arkaria.postgresql.org; Sat, 10 May 2025 11:01:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uDhxH-002BNq-U9 for pgsql-hackers@lists.postgresql.org; Sat, 10 May 2025 11:01:19 +0000 Received: from mail-oo1-xc2f.google.com ([2607:f8b0:4864:20::c2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uDhxF-0016Pi-1q for pgsql-hackers@lists.postgresql.org; Sat, 10 May 2025 11:01:19 +0000 Received: by mail-oo1-xc2f.google.com with SMTP id 006d021491bc7-605f7d3215cso1533016eaf.0 for ; Sat, 10 May 2025 04:01:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1746874877; x=1747479677; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pEwYZAkrcZkQFwJSJHW86Soj0om9LBBEHktko/rJTsA=; b=fDDkv91W5XVxmvBxuR87Ays01ANm7U+yvf+FOr+TlDZIrCubCc9PohUwJqTGsBTmnj 8JUavTqnWnzLEW8H1y3MZ3Ij1vw79z72lYZdXJxDFN4vx6MpXdL0JOd8GR4KsTBuUwEQ Yci/jszwCqo9z33jkLu8BOAZIE4V239XMTpRzhfV12IERqCDws2o36G2Pvl3aV66C8yp qEgYt9IwU1V9oRBPsd4cZXO1UvvU+2EwsMsalk84O1JRlbzQ+I/iAudgs4eDbuWcNoQ8 wB4akWROYKXEIybGFwsAdVXs93S+JfZPZSblfhDQQFSmuOf3qsp59qwMTN3ZKWF9kHBy 4Nqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1746874877; x=1747479677; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pEwYZAkrcZkQFwJSJHW86Soj0om9LBBEHktko/rJTsA=; b=VNGjeg7SbRNAEe+v9hJfxYX5Kdlyc6k0ZfLyZqLapib6AxnMKmH9EL+EzbwMMdnLM+ RX9F+oMelkS21Hp3RG81HvJ9pGBjd9km7XsbD/tWrDZRI9Nz+Yjb4Af3POXgrY/EO4Xq JiZIo8V3YHusIL5xLp4V/PnFCycaR65OPP1VGUtHLvFcNqvKeuiIcMZ2Txq2X8buAp10 JP9v+LenyMQhN0Qfa6oT7PgGyElr2hLUZMjyVzVEQ6nFb5FLFXvQsh2+85aL/gkK0vwB 3jGqEno/nMm3GqZXHOzSW/yrJwKJtFG61JcjHyjBDr2JB1SYZVmE0PO4pJAcimLxAwLF Mp/w== X-Gm-Message-State: AOJu0YxnN37jxYDQyR3qyGJ2PVBcpO3EltHzfzYXtLEGhZGAB/VSuqNP 4IW/WJqJQ+caQ4+QZKawglKdyCTfJKLbufkFGqmNVsDqFpGvdi7Ve50O9FDs63fME/sbXbQmDuA /qy0qy1Kt4bHRcGWtSYB1hFGaIl0= X-Gm-Gg: ASbGncvKBAzcHDlYY7GKheVtAPrQfuk1dAE3dRWZEzRwPMNPGrDTX4Lmq13LndhPhFB 2nboHhsj+54EtGAD9+A3QIlym14p+p7vuYdQbZPpyEZ84JjpNbP4QczFmEXXSZR6hwnqJoV5Dmb rj8TNvaGsyaCpAJSlXQr9ZFq/nQEokWOIEXA== X-Google-Smtp-Source: AGHT+IF1l+qjqN2ac9nJvMMR2LLAZooatWRJ76crPNVxqm47EeR7sHbs9Xq+cGm/17FnA367Lq+1CCYguS0tHG45E8Q= X-Received: by 2002:a05:6820:1e84:b0:604:30f2:5c48 with SMTP id 006d021491bc7-6084c111a83mr4035602eaf.7.1746874877079; Sat, 10 May 2025 04:01:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Stepan Neretin Date: Sat, 10 May 2025 18:01:06 +0700 X-Gm-Features: AX0GCFvp063VwLg6CKyI8BUv98rTXKGj17RS4470vOv2T_8KBxfFUSVFmrwiwBE Message-ID: Subject: Re: Proposal for enabling auto-vectorization for checksum calculations To: Matthew Sterrett Cc: pgsql-hackers@lists.postgresql.org, "Devulapalli, Raghuveer" , "Shankaran, Akash" Content-Type: multipart/alternative; boundary="00000000000083f63c0634c600d1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000083f63c0634c600d1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, May 8, 2025 at 6:57=E2=80=AFAM Matthew Sterrett wrote: > Hello! I'm still trying to figure out those CI failures, I just wanted > to update things. > > From my testing, with this patch repeatedly disabling/enabling > checksums is about 12.4% on an approximately 15 GB database. > > By the way, I'd love it if anyone could help me figure out how to > replicate a CI failure in the Cirrus CI. > I haven't been able to figure out how to test CI runs locally, does > anyone know a good method to do that? > > > Hi Matthew, Thanks for the patch! I ran some timing tests: (without avx2) Time: 4034.351 ms SELECT drive_pg_checksum(512); (with avx2) Time: 3559.076 ms SELECT drive_pg_checksum(512); Also attached two patches that should fix the CI issues. Best, Stepan Neretin --00000000000083f63c0634c600d1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, May 8, = 2025 at 6:57=E2=80=AFAM Matthew Sterrett <matthewsterrett2@gmail.com> wrote:
Hello! I'm still trying to fi= gure out those CI failures, I just wanted
to update things.