Re: Dramatic change in memory usage with version 9.1

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Rafael Martinez" <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>
Cc: <pgsql-performance(at)postgresql(dot)org>, "Craig Ringer" <ringerc(at)ringerc(dot)id(dot)au>
Subject: Re: Dramatic change in memory usage with version 9.1
Date: 2011-12-21 18:54:32
Message-ID: 4EF1D7080200002500043F83@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Wed, Dec 21, 2011 at 10:50 AM, Rafael Martinez
> <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> wrote:
>> As long as I know, all the databases are using the default, "read
>> committed".
>
> Note that backups run in serializable mode.

In 9.1 they default to running in "repeatable read". You can choose
the --serializable-deferrable option, which runs at the serializable
transaction isolation level, sort of. It does that by waiting for a
"safe" snapshot and then running the same as a repeatable read
transaction -- so either way you have none of the overhead of the
new serializable transactions.

Besides that, almost all of the additional RAM usage for the new
serializable implementation is in shared memory. As you can see in
the graphs from Rafael, the difference isn't very dramatic as a
percentage of a typical production configuration.

-Kevin

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Havasvölgyi Ottó 2011-12-21 23:29:16 Re: Dramatic change in memory usage with version 9.1
Previous Message Scott Marlowe 2011-12-21 18:18:21 Re: Dramatic change in memory usage with version 9.1