On 08/14/2011 08:51 AM, t...@fuzzy.cz wrote:
I've increased the test duration to 10 minutes, decreased the
checkpoint timeout to 4 minutes and a checkpoint is issued just before
the pgbench. That way the starting position should be more or less the
same for all runs.
That's basically what I
writes:
> On 13 Srpen 2011, 5:09, Greg Smith wrote:
>> And I keep seeing too many data corruption issues on ext4 to recommend
>> anyone use it yet for PostgreSQL, that's why I focused on XFS. ext4
>> still needs at least a few more months before all the bug fixes it's
>> gotten in later kernels a
On Sun, 14 Aug 2011 07:15:00 -0600, Scott Marlowe
wrote:
> On Sun, Aug 14, 2011 at 6:51 AM, wrote:
>>
>> I've increased the test duration to 10 minutes, decreased the
>> checkpoint timeout to 4 minutes and a checkpoint is issued just before
>> the pgbench. That way the starting position should b
On Sun, Aug 14, 2011 at 6:51 AM, wrote:
>
> I've increased the test duration to 10 minutes, decreased the
> checkpoint timeout to 4 minutes and a checkpoint is issued just before
> the pgbench. That way the starting position should be more or less the
> same for all runs.
Also look at increasing
On 13 Srpen 2011, 5:09, Greg Smith wrote:
> The long pauses are most likely every client blocking once the
> checkpoint sync runs. When those fsync calls go out, Linux will freeze
> for quite a while there on ext3. In this example, the drop in TPS/rise
> in latency at around 50:30 is either the b
