Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TeRF2-0000A3-Ma for pgsql-performance@arkaria.postgresql.org; Fri, 30 Nov 2012 14:06:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TeRF2-0003Zw-7S for pgsql-performance@arkaria.postgresql.org; Fri, 30 Nov 2012 14:06:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TeRF1-0003Zo-Ea for pgsql-performance@postgresql.org; Fri, 30 Nov 2012 14:06:55 +0000 Received: from smtp.optionshouse.com ([38.98.137.6] helo=smtp.peak6.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TeREy-0001ML-BV for pgsql-performance@postgresql.org; Fri, 30 Nov 2012 14:06:55 +0000 X-AuditID: 0a64cb20-b7fe66d000002e97-e3-50b8bd7a978b Message-ID: <50B8BD78.9050805@optionshouse.com> Date: Fri, 30 Nov 2012 08:06:48 -0600 From: Shaun Thomas Reply-To: Organization: Peak6 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: Vitalii Tymchyshyn CC: =?UTF-8?B?TmllbHMgS3Jpc3RpYW4gU2NoasO4ZHQ=?= , Kevin Grittner , , Willem Leenen Subject: Re: Optimize update query References: <20121130012426.69300@gmx.com> <855F8817-6C9A-4EFB-BB80-752BF7B73B56@autouncle.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed content-transfer-encoding: 7bit X-Originating-IP: [10.10.201.64] X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMKsWRmVeSWpSXmKPExsXClcIroVu1d0eAQddLRYuXx+4wWyzddZbF 4vrMc8wW60++ZbPYuW4viwOrR+fh86weO2fdZfd43HOGzWPGk9OsHhf2TWMPYI1qYLRJzMvL L0ksSVVISS1OtlXyLyjJzM8r9sgvLU5VcMksTs5JzMxNLVJSyEyxVTJWUijISUxOzU3NK7FV SiwoSM1LUbLjUsAANkBlmXkKqXnJ+SmZeem2Sp7B/roWFqaWuoZKdvHIIKGTJaN1p2XBBLaK ps17WRsYP7J0MXJySAiYSCz/u4sNwhaTuHBvPZjNK6AvMWt2G1ANBweLgKrEpvvJIGE2AV2J Sf0rwEqEBFQk+s7eYAKx+QWEJfZ9aGIGsUUFwiTW7DnEBDFGUOLkzCdgq0QENCXmf10LVMPF wSxwhFFix4yzYAlhAR2Jpk3XWSGG3mSU6NupCWJzCgRKHPq2kRHEZhawkFj85iA7hC0vsf3t HGaIelWJFc0Toe5XkPh/5R3TBEahWUh2z0LSPgtJ+wJG5lWM4sVlickZmaYFxbklBUZ6BamJ 2WZ6eaklmxjBMX9aYQfj906rQ4wCHIxKPLwLFm0PEGJNLCuuzD3EKMHBrCTC+3fjjgAh3pTE yqrUovz4otKc1OJDjD7AMJvILCWanA9MR3kl8YbGpgamlqaGpuamhkY4hJXEeUNDFwUICaQD E0l2ampBahHMOCYOTqkGxt3b3/1/cmSr46Qjn13NZGeEfoqP+qZ1YUJ08Gqn9R3OW8JjJ1a9 vF3s2VFpdWjXlZ+82erPniTE5XOKiVx5ksXq3PCoKfVGZFV8kEhJqeKzyX/kF5w/9aGrXuRs SXSJMK+EfELJkpz5O+Scb21/n2FbztX91Yh1cX5bzEmXuxpvPOdzbetkVGIpzkg01GIuKk4E ADldX2YmAwAA X-Pg-Spam-Score: -2.3 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 11/30/2012 02:37 AM, Vitalii Tymchyshyn wrote: > Actually, what's the point in putting logs to ssd? SSDs are good for > random access and logs are accessed sequentially. While this is true, Niels' problem is that his regular HDs are getting saturated. In that case, moving any activity off of them is an improvement. Why not move the data to the SSDs, you ask? Because he bought two 3TB drives. The assumption here is that a 256GB SSD will not have enough space for the long-term lifespan of this database. Either way, based on the iostat activity he posted, clearly there's some other write stream happening we're not privy to. -- Shaun Thomas OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604 312-444-8534 sthomas@optionshouse.com ______________________________________________ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance