Re: PostgreSQL caching - Mailing list pgsql-performance

From Vitaly Belman
Subject Re: PostgreSQL caching
Date
Msg-id 3115838500.20040526210034@012.net.il
Whole thread Raw
In response to Re: PostgreSQL caching  (Josh Berkus <josh@agliodbs.com>)
Responses Re: PostgreSQL caching
List pgsql-performance
Hello Josh,

JB> Not that you can't improve the query, just that it might not fix
JB> the problem.

Yes, I'm aware it might be slower than the Linux version, but then, as
you said, I still can improve the query (as I did with your help now).

But true, if there's something awfully wrong with Win32 port
performance, I might be doing some overwork...

JB> Therefore ... your detailed feedback is appreciated, especially if you can
JB> compare stuff to the same database running on a Linux, Unix, or BSD machine.

I can't easily install Linux right now.. But I am considering using it
through VMWare. Do you think it would suffice as a comprasion?

From what I saw (e.g
http://usuarios.lycos.es/hernandp/articles/vpcvs.html) the performance
are bad only when it's coming to graphics, otherwise it looks pretty
good.

Regards,
 Vitaly Belman
 
 ICQ: 1912453
 AIM: VitalyB1984
 MSN: tmdagent@hotmail.com
 Yahoo!: VitalyBe

Wednesday, May 26, 2004, 7:17:35 PM, you wrote:

JB> Vitaly,

>> I am using the newer 7.5dev native Windows port. For this reason I
>> don't think that IN will cause any trouble (I read that this issue was
>> resolved in 7.4).

JB> Well, for performance, all bets are off for the dev Windows port.   Last I
JB> checked, the Win32 team was still working on *stability* and hadn't yet even
JB> looked at performance.  Not that you can't improve the query, just that it
JB> might not fix the problem.

JB> Therefore ... your detailed feedback is appreciated, especially if you can
JB> compare stuff to the same database running on a Linux, Unix, or BSD machine.


pgsql-performance by date:

Previous
From: Chris Browne
Date:
Subject: Re: tuning for AIX 5L with large memory
Next
From: "Matthew Nuzum"
Date:
Subject: Re: PostgreSQL caching