Re: pgbench-ycsb

From: a(dot)bykov(at)postgrespro(dot)ru
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgbench-ycsb
Date: 2018-07-22 17:16:55
Message-ID: f3af6ca02beb61ed66ec8acb87e3d72f@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-07-22 16:56, Fabien COELHO wrote:
>> Just to clarify - if I understand Anthony correctly, this proposal is
>> not about
>> implementing exactly YCSB as it is, but more about using zipfian
>> distribution
>> for an id in the regular pgbench table structure in conjunction with
>> read/write
>> balance to simulate something similar to it.
>
> Ok, I misunderstood. My 0.02€: If it does not implement YCSB, and the
> point is not to implement YCSB, then do not call it YCSB:-)
>
> Maybe there could be other simpler builtins to use non uniform
> distributions: {zipf,exp,...}-{simple,select} and default values
> (exp_param, zipf_param?) for the random distribution parameters.
>
> \set id random_zipfian(1, 100000*:scale, :zipf_param)
> \set val random(-5000, 5000)
> UPDATE pgbench_whatever ...;
>
> Then
>
> pgbench -b zipf-se(at)1 -b zipf-si(at)1 [ -D zipf_param=1.1 ... ] -T 10000
> ...
>
>> And probably instead of implementing the exact YCSB workload inside
>> pgbench, it
>> makes more sense to add PostgreSQL Jsonb as one of the options into
>> the
>> framework itself (I was in the middle of it few years ago, but then
>> was
>> distracted by some interesting benchmarking results).
>
> Sure.

Hello,
thank you for your interest. I'm still improving this idea, the patch
and I'm very happy about the discussion we have. It really helps.

The idea was to implement the workloads as close to YCSB as possible
using pgbench.

So, the schema it should be applied to - is default schema generated by
pgbnench -i (pgbench_accounts).

--
Anthony Bykov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2018-07-22 17:38:57 Re: Non-portable shell code in pg_upgrade tap tests
Previous Message Andrei Korigodski 2018-07-22 17:11:59 Re: pgbench: improve --help and --version parsing