wal_buffers: 32M
effective_io_concurrency: 4
There is no bloat.
Note that we are using Postgres inside a VM, there is a VMFS layer on top
of the LUNs which might affect the performance. That said, we're still
wondering if this much I/O is normal and if we can somehow reduce it.
Enabling async comm
On Wed, Jul 17, 2013 at 12:21 PM, Vasilis Ventirozos wrote:
>
>
>
> On Wed, Jul 17, 2013 at 11:52 AM, Xenofon Papadopoulos
> wrote:
>
>> Thank you for your replies so far.
>> The DB in question is Postgres+ 9.2 running inside a VM with the
>> following specs:
>>
>> 16 CPUs (dedicated to the VM)
On Wed, Jul 17, 2013 at 11:52 AM, Xenofon Papadopoulos wrote:
> Thank you for your replies so far.
> The DB in question is Postgres+ 9.2 running inside a VM with the following
> specs:
>
> 16 CPUs (dedicated to the VM)
> 60G RAM
> RAID-10 storage on a SAN for pgdata and pgarchieves, using differen
Il 17/07/2013 12:52, Xenofon Papadopoulos ha scritto:
Thank you for your replies so far.
The DB in question is Postgres+ 9.2 running inside a VM with the
following specs:
16 CPUs (dedicated to the VM)
60G RAM
RAID-10 storage on a SAN for pgdata and pgarchieves, using different
LUNs for each.
Thank you for your replies so far.
The DB in question is Postgres+ 9.2 running inside a VM with the following
specs:
16 CPUs (dedicated to the VM)
60G RAM
RAID-10 storage on a SAN for pgdata and pgarchieves, using different LUNs
for each.
We have 3 kind of queries:
- The vast majority of the que
Hi,
Il 17/07/2013 09:18, Xenofon Papadopoulos ha scritto:
In the asynchronous commit documentation, it says:
/The commands supporting two-phase commit, such as PREPARE
TRANSACTION, are also always synchronous
/
Does this mean that all queries that are part of a distributed
transaction are s
>
> In the asynchronous commit documentation, it says:
>
> *The commands supporting two-phase commit, such as PREPARE TRANSACTION,
> are also always synchronous
> *
>
> Does this mean that all queries that are part of a distributed transaction
> are synchronous?
>
Yep
> In our databases we have
In the asynchronous commit documentation, it says:
*The commands supporting two-phase commit, such as PREPARE TRANSACTION, are
also always synchronous
*
Does this mean that all queries that are part of a distributed transaction
are synchronous?
In our databases we have extremely high disk I/O, I
