X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 94B399DC984 for ; Wed, 25 Jan 2006 12:43:11 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 18974-02 for ; Wed, 25 Jan 2006 12:43:09 -0400 (AST) X-Greylist: delayed 04:41:34.005449 by SQLgrey- Received: from office1.i-free.ru (unknown [81.222.216.82]) by postgresql.org (Postfix) with ESMTP id 2AF5E9DC98B for ; Wed, 25 Jan 2006 12:43:09 -0400 (AST) Received: from [192.168.0.250] (helo=deepcore.i-free.ru) by office1.i-free.ru with smtp (Exim 3.36 #1 (Debian)) id 1F1njg-0002vl-00 for ; Wed, 25 Jan 2006 19:43:08 +0300 Date: Wed, 25 Jan 2006 19:43:09 +0300 From: Evgeny Gridasov To: pgsql-performance@postgresql.org Subject: Re: DB responce during DB dump Message-Id: <20060125194309.8cb6e5c8.eugrid@fpm.kubsu.ru> In-Reply-To: <1459.1138206118@sss.pgh.pa.us> References: <20060125150134.55589806.eugrid@fpm.kubsu.ru> <43D772BD.8080809@archonet.com> <1459.1138206118@sss.pgh.pa.us> X-Mailer: Sylpheed version 2.1.9 (GTK+ 2.6.2; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.048 required=5 tests=[AWL=0.048] X-Spam-Score: 0.048 X-Spam-Level: X-Archive-Number: 200601/432 X-Sequence-Number: 16910 All I was trying to achieve is to limit I/O rate done by pg_dump. The script is a very simple pipe rate limitter and nothing more: it reads input, but outputs data no more than at rate specified. I guess it helps because even if pg_dump outputs data at 20 mb/sec, the script won't be able to read it at rate higher than output rate. Pipe buffer is not infinitive, so pg_dump output rate and hard disk reads become almost equal the input rate of my perl script. On Wed, 25 Jan 2006 11:21:58 -0500 Tom Lane wrote: > Years ago there was some experimentation with dump-rate throttling logic > inside pg_dump itself --- there's still a comment about it in pg_dump.c. > The experiment didn't seem very successful, which is why it never got to > be a permanent feature. I'm curious to know why this perl script is > doing a better job than we were able to do inside pg_dump. -- Evgeny Gridasov Software Engineer I-Free, Russia