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.
Hi
Thanx mate Create Index seems to be the culprit.
Is it normal to just use 1 cpu tho?
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
In response to Mozzi :
Hi
Thanx mate Create Index seems to be the culprit.
Is it normal to just use 1 cpu tho?
If you have only one client, yes. If you have more then one active
connections, every connection will use one CPU. In your case: create
index can use only one CPU.
Regards,
Mozzi,
* Mozzi (mozzi.g...@gmail.com) wrote:
Thanx mate Create Index seems to be the culprit.
Is it normal to just use 1 cpu tho?
Yes, PG can only use 1 CPU for a given query or connection. You'll
start to see the other CPUs going when you have more than one connection
to the database. If
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
