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 i
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 [..
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
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
I use RHEL 4. I can not understand how the scalability related with
shared memory?
It isn't RHEL4 and shared memory. It is PostgreSQL and shared memory.
Things have changed with PostgreSQL since 7.3 (7.3 is really god awful
old) t
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>> I use RHEL 4. I can not understand how the scalability related with
>> shared memory?
> It isn't RHEL4 and shared memory. It is PostgreSQL and shared memory.
> Things have changed with PostgreSQL since 7.3 (7.3 is really god awful
> old) that all
Michael Stone wrote:
On Fri, Mar 30, 2007 at 10:00:30PM -0600, Guido Neitzer wrote:
On 30.03.2007, at 19:18, Christopher Browne wrote:
2. There are known issues with the combination of Xeon processors and
PAE memory addressing; that sort of hardware tends to be *way* less
speedy than the specs
Christopher Browne wrote:
Quoth [EMAIL PROTECTED] (Xiaoning Ding):
When I run multiple TPC-H queries (DBT3) on postgresql, I found the system
is not scalable. My machine has 8GB memory, and 4 Xeon Dual Core processor
( 8 cores in total). OS kernel is linux 2.6.9. Postgresql is 7.3.18. I
I t
pgsql 7.3 cannot take advantage of lots of shared memory, and has some
issues scaling to lots of CPUs / processes.
I use RHEL 4. I can not understand how the scalability related with
shared memory?
It isn't RHEL4 and shared memory. It is PostgreSQL and shared memory.
Things have changed wi
Scott Marlowe wrote:
On Fri, 2007-03-30 at 15:25, Xiaoning Ding wrote:
Hi all,
When I run multiple TPC-H queries (DBT3) on postgresql, I found the system
is not scalable. My machine has 8GB memory, and 4 Xeon Dual Core processor
( 8 cores in total). OS kernel is linux 2.6.9. Postgresql is 7.3
On Fri, Mar 30, 2007 at 10:00:30PM -0600, Guido Neitzer wrote:
On 30.03.2007, at 19:18, Christopher Browne wrote:
2. There are known issues with the combination of Xeon processors and
PAE memory addressing; that sort of hardware tends to be *way* less
speedy than the specs would suggest.
That
On 30.03.2007, at 19:18, Christopher Browne wrote:
2. There are known issues with the combination of Xeon processors and
PAE memory addressing; that sort of hardware tends to be *way* less
speedy than the specs would suggest.
That is not true as the current series of processors (Woodcrest and
Quoth [EMAIL PROTECTED] (Xiaoning Ding):
> When I run multiple TPC-H queries (DBT3) on postgresql, I found the system
> is not scalable. My machine has 8GB memory, and 4 Xeon Dual Core processor
> ( 8 cores in total). OS kernel is linux 2.6.9. Postgresql is 7.3.18. I
> I think it might be caused
On Fri, 2007-03-30 at 16:38, Xiaoning Ding wrote:
> Thanks guys,
>
> I update PG to 8.2.3. The results are much better now.
> 1 process :0.94 second
> 2 processes: 1.32 seconds
> 4 processes: 2.03 seconds
> 8 processes: 2.54 seconds
>
> Do you think they are good enough?
> BTW where can I fou
On Fri, 2007-03-30 at 15:25, Xiaoning Ding wrote:
> Hi all,
>
> When I run multiple TPC-H queries (DBT3) on postgresql, I found the system
> is not scalable. My machine has 8GB memory, and 4 Xeon Dual Core processor
> ( 8 cores in total). OS kernel is linux 2.6.9. Postgresql is 7.3.18. I
> run
Thanks guys,
I update PG to 8.2.3. The results are much better now.
1 process :0.94 second
2 processes: 1.32 seconds
4 processes: 2.03 seconds
8 processes: 2.54 seconds
Do you think they are good enough?
BTW where can I found some info on what 8.2.3 did to improve
scalability compared with p
Xiaoning Ding <[EMAIL PROTECTED]> writes:
> When I run multiple TPC-H queries (DBT3) on postgresql, I found the system
> is not scalable. My machine has 8GB memory, and 4 Xeon Dual Core processor
> ( 8 cores in total). OS kernel is linux 2.6.9. Postgresql is 7.3.18.
If you are not running PG 8.1
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Xiaoning Ding
>
>
> Hi all,
>
> When I run multiple TPC-H queries (DBT3) on postgresql, I
> found the system
> is not scalable. My machine has 8GB memory, and 4 Xeon Dual
> Core processor
> ( 8 cores in total). OS kernel
Hi all,
When I run multiple TPC-H queries (DBT3) on postgresql, I found the system
is not scalable. My machine has 8GB memory, and 4 Xeon Dual Core processor
( 8 cores in total). OS kernel is linux 2.6.9. Postgresql is 7.3.18. I
run multiple
q2 queries simultaneously. The results are:
1 proc
18 matches
Mail list logo
