Re: Using quicksort for every external sort run - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Using quicksort for every external sort run
Date
Msg-id CAM3SWZSo5wB0=9tT9ZwojRQhRXXkbMnqNcqtCLV-QnpUqJcUOg@mail.gmail.com
Whole thread Raw
In response to Re: Using quicksort for every external sort run  (Marc Mamin <M.Mamin@intershop.de>)
List pgsql-hackers
On Sun, Sep 6, 2015 at 1:51 AM, Marc Mamin <M.Mamin@intershop.de> wrote:
> Have you considered performances for cases where multiple CREATE INDEX are running in parallel?
> One of our typical use case are large daily tables (50-300 Mio rows) with up to 6 index creations
> that start simultaneously.
> Our servers have 40-60 GB RAM , ca. 12 CPUs and we set maintenance mem to 1-2 GB for this.
> If the create index themselves start using parallelism, I guess that we might need to review our workflow...

Not particularly. I imagine that that case would be helped a lot here
(probably more than a simpler case involving only one CREATE INDEX),
because each core would be require fewer main memory accesses overall.
Maybe you can test it and let us know how it goes.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Marc Mamin
Date:
Subject: Re: Using quicksort for every external sort run
Next
From: Pavel Stehule
Date:
Subject: Re: [PATCH] SQL function to report log message