| From: | cca5507 <cca5507(at)qq(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Add pg_lfind8_nonzero() |
| Date: | 2025-12-16 02:33:15 |
| Message-ID: | tencent_33BE9451990CBCED8313BB8150EEC290DA07@qq.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Thank you for your reply!
> Is code like this ever actually relevant for performance? In cases where the
> compiler can't also optimize the code? Unless it is a legitimate bottleneck,
> adding more complicated code to optimize the case doesn't make sense.
I just think the patch isn't that complicated.
> The benchmark really should show performance benefits in at least somewhat
> realistic cases (i.e. real users of the functions, even if the workload is a
> bit more extreme than it'd be most of the time).
Yeah, this makes sense to me. Maybe I need to think more on it.
--
Regards,
ChangAo Chen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2025-12-16 02:45:04 | Re: create table like including storage parameter |
| Previous Message | Chao Li | 2025-12-16 02:14:00 | Re: doc: create table improvements |