From: Tomas Vondra <tv@fuzzy.cz>
To: gnanam@zoniac.com
Cc: 'Tomas Vondra' <tv@fuzzy.cz>
Cc: 'Vitalii Tymchyshyn' <tivv00@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Write workload is causing severe slowdown in Production
Date: Thu, 22 Mar 2012 13:55:28 +0100
Message-ID: <c98cd98d6fc0f1c0325a05ad5b98fbb0.squirrel@sq.gransy.com> (raw)
In-Reply-To: <00b601cd0824$c8dfd6d0$5a9f8470$@com>
References: <006301cd07fd$358ebe40$a0ac3ac0$@com>
<4F6AF3FE.30407@gmail.com>
<dc1f59dfd626334d6f37d5a6ffb97bb9.squirrel@sq.gransy.com>
<008e01cd0817$06418680$12c49380$@com>
<1bbfac04d1ec4a2708e47593dc84ba8c.squirrel@sq.gransy.com>
<00b601cd0824$c8dfd6d0$5a9f8470$@com>
On 22 Březen 2012, 13:10, Gnanakumar wrote:
>> So, what else is running on the system? Because if there's 35GB RAM and
>> the shared buffers are 1.5GB, then there's about 33GB for page cache.
>> Something like 16GB would be a conservative setting.
>
> Yes, you guessed it right. Both Web server and DB server are running in
> the same machine.
>
>> I'm not saying this will fix the issues, but maybe it shows that
>> something
>> else is running on the box and maybe that's the culprit, not PostgreSQL?
>
> Based on my observations and analysis, I'm sure that database write
> operation "is" causing the slowdown, but not because of other applications
> running in the same server.
You haven't provided any clear evidence for such statement so far. Let's
wait for the vmstat/iostat logs etc.
Tomas
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-performance@postgresql.org
Cc: tv@fuzzy.cz, gnanam@zoniac.com, tivv00@gmail.com
Subject: Re: Write workload is causing severe slowdown in Production
In-Reply-To: <c98cd98d6fc0f1c0325a05ad5b98fbb0.squirrel@sq.gransy.com>
* 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