From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Xiaoning Ding <dingxn(at)cse(dot)ohio-state(dot)edu> |
Cc: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: scalablility problem |
Date: | 2007-04-02 00:26:35 |
Message-ID: | C1E08D25-5B58-4E55-B0A5-F036C5443FED@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
I may have missed this but have you tuned your postgresql
configuration ?
8.2 tuning guidelines are significantly different than 7.3
Dave
On 1-Apr-07, at 1:51 PM, Xiaoning Ding wrote:
> I repeated the test again. It took 0.92 second under 8.2.3.
> I checked system load using top and ps. There is no other
> active processes.
>
> Xiaoning
>
> Ron Mayer wrote:
>> Xiaoning Ding wrote:
>>> Postgresql is 7.3.18. [...]
>>> 1 process takes 0.65 second to finish.
>>> I update PG to 8.2.3. The results are [...] now.
>>> 1 process : 0.94 second
>> You sure about your test environment? Anything else
>> running at the same time, perhaps?
>> I'm a bit surprised that 8.2.3 would be 40% slower than 7.3.18
>> even in the single process case.
>> ---------------------------(end of
>> broadcast)---------------------------
>> TIP 2: Don't 'kill -9' the postmaster
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kostyrka | 2007-04-02 07:45:21 | Re: How to determine which indexes are not using or using seldom in database |
Previous Message | Xiaoning Ding | 2007-04-01 17:51:36 | Re: scalablility problem |