MIME-Version: 1.0
References: <aZikzQP6WPJ5Rq2S@nathan>
 <CAN55FZ3cBN_TncLVWyXAKm-KfewguN1AUjyRhoR6zL_QCxHh7A@mail.gmail.com>
 <CAKWEB6qzsZEQ4Czo9QBFiMXqdXVJknHUJwg6wjRwNzLn4+Jw0g@mail.gmail.com>
 <CAN55FZ2O2Ls==sdpROHqxWRx-PMBZ0riJ6eVKoHj8=vssTavxw@mail.gmail.com>
 <aZ3kYQnF9_u6sUQp@nathan>
 <CAN55FZ3+NYF1TkKyNtpRQuLiaauSYk9G5tA+fpruOA4-14Y_ZA@mail.gmail.com>
 <aaXrGSyq4u2d9qEC@nathan>
 <CAN55FZ2DNaKCK3Kf_kHizb2pAbQvULeDYtzaiz97B_xz7YbrkQ@mail.gmail.com>
 <aa8QlTVEDhG1JU0Z@nathan>
 <CAN55FZ08kqmA+B9pzPDy-QstxAd=cK-RqjbR3cWBjPF_8-FXAw@mail.gmail.com>
 <abBQbdFa6OsG8TGu@nathan>
 <CAN55FZ3jXs7XDsP_-v_jUBquRu4uAdheN3xcmW=WhAyKwFLSjg@mail.gmail.com>
In-Reply-To: 
 <CAN55FZ3jXs7XDsP_-v_jUBquRu4uAdheN3xcmW=WhAyKwFLSjg@mail.gmail.com>
From: KAZAR Ayoub <ma_kazar@esi.dz>
Date: Wed, 11 Mar 2026 13:19:18 +0100
Message-ID: 
 <CA+K2RuneEqoCDNMmoboDw-JU8byL0yCrppXsyPR_9mqSw5GE=Q@mail.gmail.com>
Subject: Re: Speed up COPY FROM text/CSV parsing using SIMD
To: Nazir Bilal Yavuz <byavuz81@gmail.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>,
 Manni Wood <manni.wood@enterprisedb.com>,
	Neil Conway <neil.conway@gmail.com>, Andrew Dunstan <andrew@dunslane.net>,
	Shinya Kato <shinya11.kato@gmail.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000000ae05d064cbea6c4"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BK2RuneEqoCDNMmoboDw-JU8byL0yCrppXsyPR_9mqSw5GE%3DQ%40mail.gmail.com>
Precedence: bulk

--0000000000000ae05d064cbea6c4
Content-Type: text/plain; charset="UTF-8"

On Wed, Mar 11, 2026, 12:36 PM Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:

> 0002 has an attempt to remove some branches from SIMD code but since
> it is kind of functional change, I wanted to attach that as another
> patch. I think we can apply some parts of this, if not all.
>
0002 sounds really good to have, haven't measured the diff but it's very
logical.

Another quick question though, do we need USE_NO_SIMD for any reason? I
just remembered that there's some simd paths like json that don't use it.

Regards,
Ayoub

>

--0000000000000ae05d064cbea6c4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><div class=3D"gmail_quote gmail_quote_container"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Wed, Mar 11, 2026, 12:36 PM Nazir Bil=
al Yavuz &lt;<a href=3D"mailto:byavuz81@gmail.com">byavuz81@gmail.com</a>&g=
t; wrote:</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
0002 has an attempt to remove some branches from SIMD code but since<br>
it is kind of functional change, I wanted to attach that as another<br>
patch. I think we can apply some parts of this, if not all.<br></blockquote=
></div></div><div dir=3D"auto">0002 sounds really good to have, haven&#39;t=
 measured the diff but it&#39;s very logical.</div><div dir=3D"auto"><br></=
div><div dir=3D"auto">Another quick question though, do we need USE_NO_SIMD=
 for any reason? I just remembered that there&#39;s some simd paths like js=
on that don&#39;t use it.</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">Regards,</div><div dir=3D"auto">Ayoub</div><div dir=3D"auto"><div class=
=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>

--0000000000000ae05d064cbea6c4--