On Thu, Apr 3, 2014 at 09:01:08PM +0300, Heikki Linnakangas wrote:
> >Is there something I can set in the PGSQL parameters or in the file
> >system parameters to force a steady flow of writes to disk rather
> >than waiting for a sync system call? Mounting with "commit=1" did not
> >make a differenc
On Tue, Apr 8, 2014 at 02:00:05PM +, Shaun Thomas wrote:
> So if you are on a 1GB RAID card, set it to 1GB. Once you have 1GB
> of dirty memory (from a checkpoint or whatever), Linux will begin
> flushing.
>
> This is a pretty well-known issue on Linux systems with large amounts
> of RAM. Most
> Is there something I can set in the PGSQL parameters or in the file system
> parameters to force a steady flow of writes to disk rather than waiting for
> a sync system call? Mounting with "commit=1" did not make a difference.
The PostgreSQL devs actually had a long talk with the Linux kernel de
Hi Reza,
vm.dirty_bytes indeed makes sense, but just in case: how exactly is
your ext4 mount? Particularly, have you disabled barrier?
Ilya
On Thu, Apr 3, 2014 at 8:11 PM, Reza Taheri wrote:
>> Try setting the vm.dirty_bytes sysctl. Something like 256MB might be a good
>> starting point.
--
> Try setting the vm.dirty_bytes sysctl. Something like 256MB might be a good
> starting point.
>
> This comes up fairly often, see e.g.:
> http://www.postgresql.org/message-id/flat/27C32FD4-0142-44FE-8488-
> 9f366dc75...@mr-paradox.net
>
> - Heikki
Thanks, Heikki. That sounds like my problem al
On 04/03/2014 08:39 PM, Reza Taheri wrote:
Hello PGSQL performance community,
You might remember that I pinged you in July 2012 to introduce the TPC-V
benchmark. I am now back with more data, and a question about checkpoints. As
far as the plans for the benchmark, we are hoping to release a ben
