| From: | Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Cache Hash Index meta page. |
| Date: | 2017-01-04 10:49:06 |
| Message-ID: | CAD__OugwHTCtQH7DutStXRoobBh9wW7O8sC6bQDZoAfPViyDBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 3, 2017 at 12:05 PM, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com> wrote:
As part performance/space analysis of hash index on varchar data type
with this patch, I have run some tests for same with modified pgbench.
Modification includes:
1. Changed aid column of pg_accounts table from int to varchar(x)
2. To generate unique values as before inserted stringified integer
repeatedly to fill x.
I have mainly tested for varchar(30) and varchar(90),
Below document has the detailed report on our captured data. New hash
indexes have some ~25% improved performance over btree. And, as
expected very space efficient.
--
Thanks and Regards
Mithun C Y
EnterpriseDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| hash_index_sizes_experiment_01.ods | application/vnd.oasis.opendocument.spreadsheet | 34.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2017-01-04 10:51:07 | Re: proposal: session server side variables |
| Previous Message | Craig Ringer | 2017-01-04 10:03:37 | Re: proposal: session server side variables |