pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: J. Roeleveld <joost@antarean.org>
To: pgsql-performance@postgresql.org
Subject: Re: Overusing 1 CPU
Date: Wed, 2 Jun 2010 13:48:21 +0200
Message-ID: <201006021348.21572.joost@antarean.org> (raw)
In-Reply-To: <1275478657.1818.53.camel@stefaans-laptop>
References: <1275477160.1818.48.camel@stefaans-laptop>
	<alpine.DEB.2.00.1006021222450.4083@aragorn.flymine.org>
	<1275478657.1818.53.camel@stefaans-laptop>

On Wednesday 02 June 2010 13:37:37 Mozzi wrote:
> Hi
> 
> Thanx mate Create Index seems to be the culprit.
> Is it normal to just use 1 cpu tho?

If it is a single-threaded process, then yes.
And a "Create index" on a single table will probably be single-threaded.

If you now start a "create index" on a different table, a different CPU should 
be used for that.

> 
> Mozzi
> 
> On Wed, 2010-06-02 at 12:24 +0100, Matthew Wakeling wrote:
> > On Wed, 2 Jun 2010, Mozzi wrote:
> > > This box is basically adle @ the moment as it is still in testing yet
> > > top shows high usage on just 1 of the cores.
> >
> > First port of call: What process is using the CPU? Run top on a fairly
> > wide terminal and use the "c" button to show the full command line.
> >
> > Matthew
> 



view thread (6+ messages)  latest in thread

Message-ID: <201006021348.21572.joost@antarean.org>
Permalink:  ../201006021348.21572.joost@antarean.org/
Also on:    postgresql.org/message-id/201006021348.21572.joost@antarean.org

 · 

reply

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: joost@antarean.org
  Subject: Re: Overusing 1 CPU
  In-Reply-To: <201006021348.21572.joost@antarean.org>

* 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