From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Xeon twice the performance of opteron |
Date: | 2011-03-17 16:51:37 |
Message-ID: | AANLkTikSxo6s8D65-MZkv_D7fwbLe2=9Pa13HGAS8ORV@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Mar 17, 2011 at 1:42 PM, J Sisson <sisson(dot)j(at)gmail(dot)com> 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.
It's my theory as well - you know, this could be solved by JITting
complex expressions.
Bad cache behavior in application often comes as a side-effect of
interpreted execution (in this case, of expressions, conditions,
functions). A JIT usually solves this cache inefficiency.
I know, adding any kind of JIT to pg could be a major task.
From | Date | Subject | |
---|---|---|---|
Next Message | Craig James | 2011-03-17 16:54:17 | Re: Xeon twice the performance of opteron |
Previous Message | J Sisson | 2011-03-17 16:42:09 | Re: Xeon twice the performance of opteron |