pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mladen Gogala <gogala.mladen@gmail.com>
To: Michael Loftis <mloftis@wgops.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: postgres large database backup
Date: Thu, 1 Dec 2022 08:40:52 -0500
Message-ID: <d45f9147-f694-713b-ac83-00b47a42f241@gmail.com> (raw)
In-Reply-To: <CAHDg04u0jMySKG+dN_+zpGa=_fAT-rZ2XpQPR_rOVKS7FOHMXQ@mail.gmail.com>
References: <CA+ONtZ7CdiJ2X8x_8sPHR+tz-vv7mR1uoDzLia3fzWVZA9k0JQ@mail.gmail.com>
	<9d50f118-a3dd-565a-41bd-d3056b9b90d6@gmail.com>
	<592a2c79-9728-e450-ad60-a0df7dd0f214@erven.at>
	<303273b8-6116-23b2-f26d-866e38ef1c0a@gmail.com>
	<CAHDg04u0jMySKG+dN_+zpGa=_fAT-rZ2XpQPR_rOVKS7FOHMXQ@mail.gmail.com>

On 11/30/22 20:41, Michael Loftis wrote:
>
> ZFS snapshots don’t typically have much if  any performance impact 
> versus not having a snapshot (and already being on ZFS) because it’s 
> already doing COW style semantics.
>
Hi Michael,

I am not sure that such statement holds water. When a snapshot is taken, 
the amount of necessary I/O requests goes up dramatically. For every 
block that snapshot points to, it is necessary to read the block, write 
it to the spare location and then overwrite it, if you want to write to 
a block pointed by snapshot. That gives 3 I/O requests for every block 
written. NetApp is trying to optimize it by using 64MB blocks, but ZFS 
on Linux cannot do that, they have to use standard CoW because they 
don't have the benefit of their own hardware and OS. And the standard 
CoW is tripling the number of I/O requests for every write to the blocks 
pointed to by the snapshot, for every snapshot. CoW is a very expensive 
animal, with horns.

Regards

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com

view thread (18+ messages)  latest in thread

Message-ID: <d45f9147-f694-713b-ac83-00b47a42f241@gmail.com>
Permalink:  ../d45f9147-f694-713b-ac83-00b47a42f241@gmail.com/
Also on:    postgresql.org/message-id/d45f9147-f694-713b-ac83-00b47a42f241@gmail.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: gogala.mladen@gmail.com, mloftis@wgops.com
  Subject: Re: postgres large database backup
  In-Reply-To: <d45f9147-f694-713b-ac83-00b47a42f241@gmail.com>
  References: <CA+ONtZ7CdiJ2X8x_8sPHR+tz-vv7mR1uoDzLia3fzWVZA9k0JQ@mail.gmail.com> <9d50f118-a3dd-565a-41bd-d3056b9b90d6@gmail.com> <592a2c79-9728-e450-ad60-a0df7dd0f214@erven.at> <303273b8-6116-23b2-f26d-866e38ef1c0a@gmail.com> <CAHDg04u0jMySKG+dN_+zpGa=_fAT-rZ2XpQPR_rOVKS7FOHMXQ@mail.gmail.com> <d45f9147-f694-713b-ac83-00b47a42f241@gmail.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