From: Chris Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: how to improve the performance of creating index
Date: Fri, 19 Oct 2007 08:52:05 -0400
Message-ID: <60hckngtca.fsf@dba2.int.libertyrms.com> (raw)
References: <01c601c81247$3b8c5650$b2a502f0$@ust.hk>
yinanli@cse.ust.hk ("Yinan Li") writes:
> I am trying to improve the performance of creating index.:p>
>
> I've set shared_buffers = 1024MB:p>
>
> Effective_cache_size = 1024MB:p>
>
> Work_mem = 1GB:p>
>
> Maintenance_work_mem=512MB:p>
>
> (I'm sure that the server process has received the SIGHUP signal):p>
>
> However, when create index, I found that the memory used by Postgres is only 50MB. And it is very
> slow. How to make it faster?:p>
>
> All helps are appreciated.:p>
Those values seem rather large, with the exception of the effective
cache size, which I would expect to be somewhat bigger, based on the
other values.
Note that the values for work_mem and maintenance_work_mem get used
each time something is sorted or maintained. So if those values get
set high, this can pretty easily lead to scary amounts of swapping,
which would tend to lead to things getting "very slow."
You may want to do a census as to how much resources you have on the
server. Knowing that would help people make more rational evaluations
of whether your parameters are sensible or not.
--
(reverse (concatenate 'string "moc.enworbbc" "@" "enworbbc"))
http://linuxdatabases.info/info/languages.html
All syllogisms have three parts, therefore this is not a syllogism.
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: cbbrowne@acm.org
Subject: Re: how to improve the performance of creating index
In-Reply-To: <60hckngtca.fsf@dba2.int.libertyrms.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