Re: scalablility problem

From: Xiaoning Ding <dingxn(at)cse(dot)ohio-state(dot)edu>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: scalablility problem
Date: 2007-03-31 15:54:29
Message-ID: 460E8435.3000605@cse.ohio-state.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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 would suggest.
>>
>> That is not true as the current series of processors (Woodcrest and
>> the like) are also called Xeon. You probably mean the Pentium IV era
>> Xeons.
>
> Well, the newer ones can address large amounts of memory directly,
> without using PAE, but the original comment was correct--PAE is slow
> regardless of what processor implements it.

Here is the information in /proc/cpuinfo

processor : 6
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Xeon(TM) CPU 2.80GHz
stepping : 8
cpu MHz : 2793.091
cache size : 2048 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall
nx lm pni monitor ds_cpl est cid cx16 xtpr
bogomips : 5586.08
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual

>
> Mike Stone
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
>
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Erik Jones 2007-03-31 15:56:40 Re: Shared buffers, db transactions commited, and write IO on Solaris
Previous Message Xiaoning Ding 2007-03-31 15:54:15 Re: scalablility problem