From: | 'Bruce Momjian' <bruce(at)momjian(dot)us> |
---|---|
To: | dandl <david(at)andl(dot)org> |
Cc: | 'Andres Freund' <andres(at)anarazel(dot)de>, 'Scott Marlowe' <scott(dot)marlowe(at)gmail(dot)com>, 'pgsql-general' <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: What limits Postgres performance when the whole database lives in cache? |
Date: | 2016-09-03 02:01:28 |
Message-ID: | 20160903020128.GB3838@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Sep 3, 2016 at 10:45:47AM +1000, dandl wrote:
> > Agreed. Stonebraker measured Shore DBMS, which is an academic
> > database:
> >
> > http://research.cs.wisc.edu/shore/
> >
> > If he had measured a production-quality database that had been
> > optimized like Postgres, I would take more stock of his "overhead"
> > numbers.
>
> Exactly! And that's what I'm asking: has anyone done or know of any figures for Postgres, to set against these?
Uh, well, there are Postgres tools that measure the overhead of locking
on queries and stuff. I don't know any numbers myself.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | dandl | 2016-09-03 03:36:49 | Re: What limits Postgres performance when the whole database lives in cache? |
Previous Message | dandl | 2016-09-03 00:45:47 | Re: What limits Postgres performance when the whole database lives in cache? |