Article View: comp.os.linux.hardware
Article #511Re: Dual Celeron's and SMP Performance Problems
From: Suran
Date: Wed, 26 May 1999 00:00
Date: Wed, 26 May 1999 00:00
57 lines
3005 bytes
3005 bytes
Rowan Hughes wrote: > > In article <7iette$6ge$1@nnrp03.primenet.com>, Rod Roark wrote: > >I must be dense. After reading this a couple of times I still don't > >understand: how can two Celerons be worse than one when each has its > >own cache? I don't see how an interrupt serviced by one would cause > > Well i've certainly had this experience on dual/SMP machines, > although not on X86/linux. There are many thing that can go worse than an single-systems if not written with SMP's in mind. First Cache-Trashing: (big impact) If some processors happen to work on the same data and this data is smaller than a cache-line (512Byte? don't know for intel, only guess.) if one processor updates only one byte the other has to trash this line and (scince he is working on it) get it from the first one blocking the interface to the memory and IO (bus-architecture) wich is a real performance-blocker in SMPs (that's why big SMP's often have really big cross-bared and interleaved memory interfaces with huge third-level caches.). Second Cache-Flushing: (even bigger) happens at Mutex-Locks(syncronization of multiple threads should as long as possible be handled without these) and propably interrupts (never gone this far into the mashine to know about this for shure). Third Memory-Access: Multiple processors have to syncronize and share a single (on i386 REALLY NARROW) memory-interface and all this IO-devices. If more than one processors want sth. to chew on they have to wait for each other and are probably sitting pretty idle (especially on large data-sets even an older alpha with say, 70% the fp-power of the compared intel can rush away because of this, and this is what his graph showed and it has a REALLY HUGE IMPACT scince both processors may end up cooling down and waiting for each other but that's more a problem of i386 against others that is only experienced much clearer on SMP's.). ...someone who is running a dual PII, optimizing and writing parallel and distributed software scince some time and will definately UPGRADE to a newer dual celeron. --- Suran@gmx.net
Technical Details
Message-ID:
<374C1564.BF40EF52@gmx.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<7ieko6$41e$1@nnrp1.deja.com> <7iette$6ge$1@nnrp03.primenet.com> <slrn7kmo5i.143.hughesr@nrpc.dnr.qld.gov.au>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1159f7,acbefbd0f12f9cdd X-Google-Attributes: gid1159f7,public X-Google-Thread: 102b32,acbefbd0f12f9cdd X-Google-Attributes: gid102b32,public X-Google-Thread: 100562,acbefbd0f12f9cdd X-Google-Attributes: gid100562,public From: Suran <suran@gmx.net> Subject: Re: Dual Celeron's and SMP Performance Problems Date: 1999/05/26 Message-ID: <374C1564.BF40EF52@gmx.net> X-Deja-AN: 482348473 Content-Transfer-Encoding: 7bit References: <7ieko6$41e$1@nnrp1.deja.com> <7iette$6ge$1@nnrp03.primenet.com> <slrn7kmo5i.143.hughesr@nrpc.dnr.qld.gov.au> X-Accept-Language: de,en Content-Type: text/plain; charset=us-ascii Organization: FBIN Mime-Version: 1.0 Reply-To: suran@gmx.net Newsgroups: comp.os.linux.hardware,alt.comp.hardware.overclocking,csu.unix.linux