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>
 <CA+K2RuneEqoCDNMmoboDw-JU8byL0yCrppXsyPR_9mqSw5GE=Q@mail.gmail.com>
In-Reply-To: 
 <CA+K2RuneEqoCDNMmoboDw-JU8byL0yCrppXsyPR_9mqSw5GE=Q@mail.gmail.com>
From: Nazir Bilal Yavuz <byavuz81@gmail.com>
Date: Wed, 11 Mar 2026 16:10:42 +0300
Message-ID: 
 <CAN55FZ3Umf=cu9Vs9Joyrmz90eAqf1hS2QUNch9AZTjz3oY=3Q@mail.gmail.com>
Subject: Re: Speed up COPY FROM text/CSV parsing using SIMD
To: KAZAR Ayoub <ma_kazar@esi.dz>
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: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAN55FZ3Umf%3Dcu9Vs9Joyrmz90eAqf1hS2QUNch9AZTjz3oY%3D3Q%40mail.gmail.com>
Precedence: bulk

Hi,

On Wed, 11 Mar 2026 at 15:19, KAZAR Ayoub <ma_kazar@esi.dz> wrote:
>
> 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.

I agree with you. I saw very small speedups like 1%-2% but I think
changes make sense regardless of the performance improvement.


> 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.

vector8_eq() and vector8_highbit_mask() don't have non-SIMD
implementations, so we need to use USE_NO_SIMD.


-- 
Regards,
Nazir Bilal Yavuz
Microsoft