From: | Eric Soroos <eric-psql(at)soroos(dot)net> |
---|---|
To: | Jack Coates <jack(at)lyris(dot)com> |
Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: tuning questions |
Date: | 2003-12-04 22:59:45 |
Message-ID: | 8DABDA81-26AD-11D8-8622-0003930F2A6C@soroos.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
>
> IO is active, but hardly saturated. CPU load is hefty though, load
> average is at 4 now.
>
> procs memory swap io
> system cpu
> r b w swpd free buff cache si so bi bo in cs
> us sy id
> 0 2 1 2808 11432 39616 1902984 0 0 204 876 788 507
> 3 4 93
You're getting a load average of 4 with 93% idle?
That's a reasonable number of context switches, and if the blocks
you're reading/writing are discontinous, I could see io saturation
rearing it's head.
This looks to me like you're starting and killing a lot of processes.
Is this thrashing psql connections, or is it one big query? What are
your active processes?
Your effective cache size looks to be about 1900 megs (+- binary),
assuming all of it is pg.
eric
From | Date | Subject | |
---|---|---|---|
Next Message | Jack Coates | 2003-12-04 23:16:11 | Re: tuning questions |
Previous Message | Alvar Freude | 2003-12-04 22:41:38 | Re: bytea, index and like operator again and detailed |
From | Date | Subject | |
---|---|---|---|
Next Message | Jack Coates | 2003-12-04 23:16:11 | Re: tuning questions |
Previous Message | Richard Huxton | 2003-12-04 22:45:21 | Re: Slow UPADTE, compared to INSERT |