From: | Craig James <craig_james(at)emolecules(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Xeon twice the performance of opteron |
Date: | 2011-03-17 16:54:17 |
Message-ID: | 4D823CB9.9090906@emolecules.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 3/17/11 9:42 AM, J Sisson wrote:
> On Thu, Mar 17, 2011 at 10:13 AM, Jeff<threshar(at)torgo(dot)978(dot)org> wrote:
>> hey folks,
>>
>> Running into some odd performance issues between a few of our db boxes.
> We've noticed similar results both in OLTP and data warehousing conditions here.
>
> Opteron machines just seem to lag behind *especially* in data
> warehousing. Smaller
> cache for sorting/etc... is what I'd always chalked it up to, but I'm
> open to other theories
> if they exist.
We had a similar result with a different CPU-intensive open-source package, and discovered that if we compiled it on the Opteron it ran almost twice as fast as binaries compiled on Intel hardware. We thought we could compile once, run everywhere, but it's not true. It must have been some specific optimization difference between Intel and AMD that the gcc compiler knows about. I don't know if that's the case here, but it's a thought.
Craig
From | Date | Subject | |
---|---|---|---|
Next Message | Timothy Garnett | 2011-03-17 16:55:10 | Re: Adding additional index causes 20,000x slowdown for certain select queries - postgres 9.0.3 |
Previous Message | Claudio Freire | 2011-03-17 16:51:37 | Re: Xeon twice the performance of opteron |