Thread: Optimizing Advice...Now please

Optimizing Advice...Now please

From
"KoPra Workshop"
Date:
I'm having problem in postgresql performance (response query result)
when installed on
Compaq Proliant ML350 - RAM 256 MB - No Mirror SCSI RAID

I done set postmaster config with [ -B 256 -N 128 -i -o -F -S4096]
Partition "/data" size 3 GB

Any body can advice here....? or request other information to analyze...?

Eko Pranoto



Re: Optimizing Advice...Now please

From
Stephan Szabo
Date:
Generally, we'll need schema and query in question.
Also, have you run a vacuum analyze on your data recently?

On Fri, 9 Mar 2001, KoPra Workshop wrote:

> I'm having problem in postgresql performance (response query result)
> when installed on
> Compaq Proliant ML350 - RAM 256 MB - No Mirror SCSI RAID
>
> I done set postmaster config with [ -B 256 -N 128 -i -o -F -S4096]
> Partition "/data" size 3 GB
>
> Any body can advice here....? or request other information to analyze...?
>
> Eko Pranoto
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>


Re: Optimizing Advice...Now please

From
"KoPra Workshop"
Date:

From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Cc: <pgsql-admin@postgresql.org>
>
> Generally, we'll need schema and query in question.

I'm newbie ...
your meaning with schema is the table structure....?

> Also, have you run a vacuum analyze on your data recently?
>

yes....with little losing data

Eko Pranoto


Re: Optimizing Advice...Now please

From
Stephan Szabo
Date:
On Sat, 10 Mar 2001, KoPra Workshop wrote:

>
>
> From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
> Cc: <pgsql-admin@postgresql.org>
> >
> > Generally, we'll need schema and query in question.
>
> I'm newbie ...
> your meaning with schema is the table structure....?

Yeah, basically table structure , rules, triggers and indexes (probably
just tables and indexes in most cases.
The query and the output from EXPLAIN query is useful (for example if it's
select * from foo; do an EXPLAIN select * from foo;) because it gives info
on what the optimizer thinks is the best plan.