From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: FreeBSD UFS & fsync |
Date: | 2021-03-11 14:29:45 |
Message-ID: | 20210311142945.GB2469@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, Feb 23, 2021 at 12:57:22PM +0100, Luca Ferrari wrote:
> On Tue, Feb 23, 2021 at 8:46 AM Luca Ferrari <fluca1978(at)gmail(dot)com> wrote:
> > I'm using sata disks, not scsi. Assuming I'm not looking at the wrong
> > parameter, I wil attach a scsi disk to do the same test and see if
> > something changes.
>
> I've tested the same version of PostgreSQL, same benchmark, on a scsi
> disk. However, turning off fsync does not provide any increment at all
> (something that spans in less than 1% tps).
> I've checked and I have WCE enabled on such disk, but apparently I
> cannot modify (I suspect this is due to the virtualization of the
> disk):
You should really be running pg_test_fsync for this kind of testing.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | Kamil Dziedzic | 2021-03-11 21:12:37 | Re: Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"? |
Previous Message | Michael Lewis | 2021-03-10 13:29:18 | Re: Fwd: different execution time for the same query (and same DB status) |