From: | a(dot)bykov(at)postgrespro(dot)ru |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | pgbench-ycsb |
Date: | 2018-07-19 12:46:59 |
Message-ID: | 20180719154659.4becab56@anthony-24-g082ur |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello, hackers.
It might be a good idea to give users an opportunity to test their
applications with pgbench under different real-life-like load. So that
they will be able to see what's going to happen on production.
YCSB (Yahoo! Cloud Serving Benchmark) was taken as a concept. YCSB tests
were originally designed to facilitate performance comparisons of
different cloud data serving systems and it takes into account different
application workloads like:
workload A - assumes that application do a lot of reads(50%) and
updates(50%).
workload B - case when application do 95% of cases reads
and 5% updates
workload C - models behavior of read-only application.
workload E - the workload of the applications which in 95% of cases
requests for several neighboring tuples and in 5% of cases - does
updates.
In the patch those workloads were implemented to be executed by pgbench:
pgbench -b ycsb-A
--
Anthony Bykov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Attachment | Content-Type | Size |
---|---|---|
0001-pgbench-ycsb-v3.patch | text/x-patch | 6.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2018-07-19 12:50:23 | Re: Bug in gin insert redo code path during re-compression of empty gin data leaf pages |
Previous Message | Heikki Linnakangas | 2018-07-19 12:42:24 | Re: Runtime partition pruning for MergeAppend |