I started db creation over, this time with 16GB maintenance_work_mem and
fsync=off and it does not seem to have a great effect. After again 5 hours,
during index creation, disk and cpu are barely used: 95% idle and 2-3 MB/s
writes (150 reads/s, 90 writes/s).

Sébastien

On Thu, Sep 13, 2012 at 1:29 AM, John R Pierce <pie...@hogranch.com> wrote:

> On 09/12/12 10:01 PM, Sébastien Lorion wrote:
>
>> pgbench initialization has been going on for almost 5 hours now and still
>> stuck before vacuum starts .. something is definitely wrong as I don't
>> remember it took so long first time I created the db....
>>
>
> pgbench initialization with a high scale factor, like the -s 10000 I
> frequently use, does take quite a few hours.    you need a large
> maintenance_work_mem, or the create index phase will take a really long
> time to index the 150GB worth of tables its created.
>
>
>
>
> --
> john r pierce                            N 37, W 122
> santa cruz ca                         mid-left coast
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/**mailpref/pgsql-general<http://www.postgresql.org/mailpref/pgsql-general>
>

Reply via email to