Re: [GENERAL] Fastest memmove in C

t;; Alvaro Herrera <alvhe...@2ndquadrant.com>; PostgreSQL General <pgsql-general@postgresql.org> Subject: Re: [GENERAL] Fastest memmove in C Stephen Frost <sfr...@snowman.net> writes: > While I agree with this, I'm trying to figure out why this isn't being > incorporated into

Re: [GENERAL] Fastest memmove in C

Stephen Frost writes: > While I agree with this, I'm trying to figure out why this isn't being > incorporated into glibc instead..? Indeed --- it seems far more useful to integrate this sort of work at the libc level than to ask applications to support their own replacements

Re: [GENERAL] Fastest memmove in C

* Merlin Moncure (mmonc...@gmail.com) wrote: > Well, testing is the key here. Microbechmarks demonstrating the value > are not enough; proven statistically relevant benchmarks generated > from postgres are the data points needed to make an assessment. My > recommendation would be to dynamically

Re: [GENERAL] Fastest memmove in C

On Thu, Jul 7, 2016 at 6:12 AM, FarjadFarid(ChkNet) wrote: > > > Hi Álvaro, > > Based on the article. This research has been tested with various hardware. > The code automatically detects the hardware and based on the size of memory > to be copied it will choose

Re: [GENERAL] Fastest memmove in C

ra Sent: 06 July 2016 22:15 To: FarjadFarid(ChkNet) <farjad.fa...@checknetworks.com> Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Fastest memmove in C FarjadFarid(ChkNet) wrote: > Excellent research and could be well worth checking out. As it could > improve the performance of

Re: [GENERAL] Fastest memmove in C

FarjadFarid(ChkNet) wrote: > Excellent research and could be well worth checking out. As it could > improve the performance of postgresql engine. 0) We certainly do a lot of memory copying. 1) this work is under the "Code Project Open License" which doesn't look compatible with our Postgres

Re: [GENERAL] Fastest memmove in C

Just came across this excellent research work done on memmove by T Herselman. Bearing in mind memory is constantly moved in any database. This excellent set of library would be very handy for those who work at the deep end of postgresql. In a nut shell, the library checks the