From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Mike Sofen <msofen@runbox.com>
To: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: Postgres bulk insert/ETL performance on high speed servers - test results
Date: Wed, 7 Sep 2016 14:22:10 -0500
Message-ID: <d2676efc-d67a-4960-d07f-59d3db7588a2@BlueTreble.com> (raw)
In-Reply-To: <001401d206a8$9eda1350$dc8e39f0$@runbox.com>
References: <MWHPR10MB130991B6EE45A43B50E081EFDDE20@MWHPR10MB1309.namprd10.prod.outlook.com>
<04b701d204c2$0bd7e330$2387a990$@runbox.com>
<CAGTBQpa+go_gT2=H7JJROTY-qpo8x12JLNP-L46kaRMuk14zZg@mail.gmail.com>
<001401d206a8$9eda1350$dc8e39f0$@runbox.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 9/4/16 7:34 AM, Mike Sofen wrote:
> You raise a good point. However, other disk activities involving large
> data (like backup/restore and pure large table copying), on both
> platforms, do not seem to support that notion. I did have both our IT
> department and Cisco turn on instrumentation for my last test, capturing
> all aspects of both tests on both platforms, and I’m hoping to see the
> results early next week and will reply again.
Something important to remember about Postgres is that it makes
virtually no efforts to optimize IO; it throws the entire problem in the
OSes lap. So differences in OS config or in IO *latency* can have a
massive impact on performance. Because of the sensitivity to IO latency,
you can also end up with a workload that only reports say 60% IO
utilization but is essentially IO bound (would be 100% IO utilization if
enough read-ahead was happening).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: Jim.Nasby@BlueTreble.com, msofen@runbox.com
Subject: Re: Postgres bulk insert/ETL performance on high speed servers - test results
In-Reply-To: <d2676efc-d67a-4960-d07f-59d3db7588a2@BlueTreble.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