Re: Best COPY Performance
От
Stefan Kaltenbrunner
Тема
Re: Best COPY Performance
Дата
Msg-id
45462710.3000301@kaltenbrunner.cc
Ответ на
Re: Best COPY Performance (Luke Lonergan)
Список
Дерево обсуждения
Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance Markus Schaber <schabi@logix-tt.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance Markus Schaber <schabi@logix-tt.com>
Re: Best COPY Performance "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Michael Artz" <mlartz@gmail.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance Teemu Torma <teemu@torma.org>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Joshua D. Drake" <jd@commandprompt.com>
Re: Best COPY Performance "Craig A. James" <cjames@modgraph-usa.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Craig A. James" <cjames@modgraph-usa.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Craig A. James" <cjames@modgraph-usa.com>
Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Russell Smith <mr-russ@pws.com.au>
Re: Postgres server crash Richard Huxton <dev@archonet.com>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Tom Lane <tgl@sss.pgh.pa.us>
Re: Postgres server crash Richard Troy <rtroy@ScienceTools.com>
Re: Postgres server crash Michael Stone <mstone+postgres@mathom.us>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Michael Stone <mstone+postgres@mathom.us>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Bruno Wolff III <bruno@wolff.to>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Richard Broersma Jr <rabroersma@yahoo.com>
Re: Postgres server crash Michael Stone <mstone+postgres@mathom.us>
Re: Postgres server crash "Jim C. Nasby" <jim@nasby.net>
Re: Postgres server crash Michael Stone <mstone+postgres@mathom.us>
Re: Postgres server crash Florian Weimer <fw@deneb.enyo.de>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Tom Lane <tgl@sss.pgh.pa.us>
Re: Postgres server crash Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Postgres server crash Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Postgres server crash Markus Schaber <schabi@logix-tt.com>
Re: Postgres server crash Richard Huxton <dev@archonet.com>
Re: Postgres server crash Ben <bench@silentmedia.com>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Richard Huxton <dev@archonet.com>
Re: Postgres server crash Tom Lane <tgl@sss.pgh.pa.us>
Re: Postgres server crash "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance Alex Stapleton <alexs@advfn.com>
Luke Lonergan wrote: > Stefan, > > On 10/30/06 8:57 AM, "Stefan Kaltenbrunner" wrote: > >>> We've found that there is an ultimate bottleneck at about 12-14MB/s despite >>> having sequential write to disk speeds of 100s of MB/s. I forget what the >>> latest bottleneck was. >> I have personally managed to load a bit less then 400k/s (5 int columns >> no indexes) - on very fast disk hardware - at that point postgresql is >> completely CPU bottlenecked (2,6Ghz Opteron). > > 400,000 rows/s x 4 bytes/column x 5 columns/row = 8MB/s > >> Using multiple processes to load the data will help to scale up to about >> 900k/s (4 processes on 4 cores). yes I did that about half a year ago as part of the CREATE INDEX on a 1,8B row table thread on -hackers that resulted in some some the sorting improvements in 8.2. I don't think there is much more possible in terms of import speed by using more cores (at least not when importing to the same table) - iirc I was at nearly 700k/s with two cores and 850k/s with 3 cores or such ... > > 18MB/s? Have you done this? I've not seen this much of an improvement > before by using multiple COPY processes to the same table. > > Another question: how to measure MB/s - based on the input text file? On > the DBMS storage size? We usually consider the input text file in the > calculation of COPY rate. yeah that is a good questions (and part of the reason why I cited the rows/sec number btw.) Stefan
В списке pgsql-performance по дате отправления