pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Ildar Musin <i.musin@postgrespro.ru>
To: pgsql-hackers@lists.postgresql.org
Cc: Teodor Sigaev <teodor@sigaev.ru>
Subject: Re: General purpose hashing func in pgbench
Date: Wed, 14 Mar 2018 15:30:46 +0300
Message-ID: <c5c0366e-6d66-df0e-a54f-a16081d582c5@postgrespro.ru> (raw )
In-Reply-To: <7b1b71c7-e308-b39f-e386-d6d67d276071@postgrespro.ru >
References: <0e8bd39e-dfcd-2879-f88f-272799ad7ef2@postgrespro.ru >
<alpine.DEB.2.20.1801101903150.15856@lancre >
<291822a3-0b3a-0b21-c694-c10776f516ac@postgrespro.ru >
<6e47c84a-d42a-0e08-1b0d-33e6a6c87778@postgrespro.ru >
<alpine.DEB.2.20.1801121614470.13422@lancre >
<bca39e87-6d40-98f6-e4ef-e2d88e109f9c@postgrespro.ru >
<alpine.DEB.2.20.1801170727240.11884@lancre >
<960a8096-dde5-5175-7d7c-ef151086cbee@postgrespro.ru >
<alpine.DEB.2.20.1801180710400.11884@lancre >
<ae0c93b1-f8a8-a9aa-244c-0c872fa789f0@postgrespro.ru >
<alpine.DEB.2.20.1801260714070.26762@lancre >
<12986cad-3dd9-a449-e318-4acd8a8e1697@postgrespro.ru >
<alpine.DEB.2.20.1801280851260.17596@lancre >
<b2dd64bb-2d74-bde4-97df-fa1f57f079eb@postgrespro.ru >
<alpine.DEB.2.20.1801291301500.31442@lancre >
<736d5e10-8823-a0f8-574e-3ebd7c4a4920@postgrespro.ru >
<1ad42902-ef1f-a715-7010-1288fb8aae89@sigaev.ru >
<75f45845-24ed-347b-66d5-2f18d39c6793@postgrespro.ru >
<7b1b71c7-e308-b39f-e386-d6d67d276071@postgrespro.ru >
Hello Teodor,
On 07.03.2018 16:21, Ildar Musin wrote:
> Turned out that the only big-endian machine I could run test on is
> out of order.
I finally managed to perform this test on sparc v9 machine which is 64
bit big-endian architecture. I run pgbench script (see previous message)
with default_seed=123 on both x86-64 and sparc machines and visualized
the results. You can find them in the attached chart. Both images showed
the same distribution. So endianness isn't a concern here.
Thanks!
--
Ildar Musin
i.musin@postgrespro.ru
Attachments:
pgbench_hash_sparc_vs_x86.png (image/png, 46.3K) download
view image
view thread (44+ messages) latest in thread
Message-ID: <c5c0366e-6d66-df0e-a54f-a16081d582c5@postgrespro.ru>
Permalink: ../c5c0366e-6d66-df0e-a54f-a16081d582c5@postgrespro.ru/
Also on: postgresql.org/message-id/c5c0366e-6d66-df0e-a54f-a16081d582c5@postgrespro.ru
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: i.musin@postgrespro.ru, pgsql-hackers@lists.postgresql.org, teodor@sigaev.ru
Subject: Re: General purpose hashing func in pgbench
In-Reply-To: <c5c0366e-6d66-df0e-a54f-a16081d582c5@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox