pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Tomas Vondra <tv@fuzzy.cz>
To: pgsql-hackers@postgresql.org
Subject: Re: GIN improvements part2: fast scan
Date: Sun, 09 Feb 2014 22:35:01 +0100
Message-ID: <52F7F485.6010902@fuzzy.cz> (raw )
In-Reply-To: <CAF4Au4xW-peajLZA822qiTkOw4y6GoJ4GRpT8XFXj+zB1S-b_w@mail.gmail.com >
References: <CAPpHfdvftaJq7www381naLw1=4u0h+qpXgWvNhcEB9HMVywbGg@mail.gmail.com >
<51D00FB6.9030008@vmware.com >
<CAPpHfdtsDe-O6oQdCZUh6N1gGOMz0XKTMNQro-fueg-R06PaWw@mail.gmail.com >
<528533D9.3040501@vmware.com >
<CAPpHfduOvUFT+GgCrnBOzRR19eTb9mDsDJwU=S0h477fdgr=RA@mail.gmail.com >
<CAPpHfdtZOhsmz_uf5BfdXcj5W3zk3K-PYxFc8-7eQw-nPXX1DA@mail.gmail.com >
<CAPpHfdsEKFmrOU51EWSbF-RDESasSVa2YjoyFoG+0jCZOn1qjw@mail.gmail.com >
<CAPpHfdvs-EHiwmTgfK=uJ4W3OjskVHyfkuehtyrKfKY_KmMpVw@mail.gmail.com >
<52E141BA.5000302@vmware.com >
<52E4141E.60609@fuzzy.cz >
<52E42AD0.5060600@vmware.com >
<52E4AA3A.9000607@fuzzy.cz >
<52E53458.2010106@vmware.com >
<CAPpHfdticvY2+RGTxzQdrr4YSQie+vYGRDRBTuG1ZxBmjwGrOA@mail.gmail.com >
<CAPpHfduivz3MOA8_o+44n_Z0P-n+WCW=K1DrH+-g3gb-cbM2aA@mail.gmail.com >
<52E72A10.5040908@fuzzy.cz >
<52EE21D1.2080804@vmware.com >
<52EED0FC.2060503@fuzzy.cz >
<52EEF472.9020106@fuzzy.cz >
<CAF4Au4xW-peajLZA822qiTkOw4y6GoJ4GRpT8XFXj+zB1S-b_w@mail.gmail.com >
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 3.2.2014 07:53, Oleg Bartunov wrote:
> Tomasa, it'd be nice if you use real data in your testing.
>
> One very good application of gin fast-scan is dramatic performance
> improvement of hstore/jsonb @> operator, see slides 57, 58
> http://www.sai.msu.su/~megera/postgres/talks/hstore-dublin-2013.pdf .
> I'd like not to lost this benefit :)
>
> Oleg
>
> PS. I used data delicious-rss-1250k.gz from
> http://randomwalker.info/data/delicious/
Hi Oleg,
I'm working on extending the GIN testing to include this test (and I'll
use it to test both for GIN and hstore-v2 patches).
I do have the dataset, but I need the queries too - how did you generate
the queries for your benchmark? Do you have some query generator at hand?
In your Dublin talk I see just this query type
select count(*) from hs where h @> 'tags=>{{term=>NYC}}';
but that seems inadequate for representative benchmark. Are there other
types of queries that need to be tested / might be interesting? E.g.
queries with multiple search terms etc.?
regards
Tommas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
view thread (90+ messages) latest in thread
Message-ID: <52F7F485.6010902@fuzzy.cz>
Permalink: ../52F7F485.6010902@fuzzy.cz/
Also on: postgresql.org/message-id/52F7F485.6010902@fuzzy.cz
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: tv@fuzzy.cz
Subject: Re: GIN improvements part2: fast scan
In-Reply-To: <52F7F485.6010902@fuzzy.cz>
* 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