🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: aus.computers.linux
Article #260

Re: Dual processors ?

#260
From: Christopher Browne
Date: Sun, 05 Jan 2003 03:51
52 lines
3921 bytes
Quoth George Bell <MasterofTimeADim@netscape.net>:
> While I generally agree that dual CPU may be inappropriate, this is
> an inaccurate statement.  The allocation of CPU resources is a
> function of the os, not the tasks running(and thus the software).
> Since Linux can support SMP - symetric multiprocessor( each
> processor gets as much "work" as the other ), then twice as much CPU
> time is available to the system and the performance is twice as
> great, period.

This isn't a fair assessment of things.  

Having a second CPU /may/ allow the kernel to push tasks onto one CPU
or another, sharing the load.  If you have a whole bunch of processes
that /can/ run in parallel, that can be useful.

On the other hand, the two CPUs have to share:
 a) The same memory bus;
 b) The same memory caches;
 c) The same I/O buses.

If the CPUs are working on totally different sorts of things, b) can
lead in particular to "sucky performance."

Consider: on a single CPU machine, any given task is going to get a
bunch of cycles to work on whatever is the work of the task.  When a
context switch occurs, different activity will lead to different cache
usage, but at least you get locality of access within the process
context.

On a dual CPU machine, two processes really are running concurrently,
and if their accesses to memory are really quite different, they'll be
stumbling over each other as they concurrently try to access very
different things in memory.

Both CPUs have to coordinate their access to memory lest they get out
of sync and start trampling on each others' memory.  That coordination
effort has a cost, and it is a cost that a single CPU machine does not
need to pay.

If both CPUs are /reading/ the same code, or /reading/ the same memory
locations, there could conceivably be a big /WIN/ as a result; the
first CPU already read the data, so it's in cache so that the second
CPU doesn't have to read it in.  But that is not the typical case; it
is more likely that you'll have XFree86 on one CPU, doing its thing,
and Mozilla on the other, doing something different, so that
maintaining cache coherency is a net /cost/.
-- 
(concatenate 'string "cbbrowne" "@acm.org")
http://www3.sympatico.ca/cbbrowne/oses.html
I was  thinking about how  people seem to  read the Bible a  whole lot
more as they  get older then it dawned on  me...they were cramming for
their finals.
Technical Details
Message-ID: <av8a3u$d2h2f$1@ID-125932.news.dfncis.de>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!fu-berlin.de!uni-berlin.de!hse-mtl-ppp74247.qc.sympatico.CA!not-for-mail
References: <pan.2003.01.03.13.58.10.249319@iprimus.com.au> <av578p$c8s17$1@ID-99293.news.dfncis.de> <av5qtf$tcf$1@lust.ihug.co.nz> <fbf82913.0301040421.1a35bdfa@posting.google.com> <3E178C63.7040901@netscape.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 114381,acfea8e5e9ff6f15
X-Google-Attributes: gid114381,public
X-Google-Thread: 102b32,acfea8e5e9ff6f15
X-Google-Attributes: gid102b32,public
X-Google-Thread: 102983,acfea8e5e9ff6f15
X-Google-Attributes: gid102983,public
X-Google-ArrivalTime: 2003-01-04 19:51:28 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!fu-berlin.de!uni-berlin.de!hse-mtl-ppp74247.qc.sympatico.CA!not-for-mail
From: Christopher Browne <cbbrowne@acm.org>
Newsgroups: aus.computers.linux,comp.os.linux.hardware,aus.ads.forsale.computers.used
Subject: Re: Dual processors ?
Date: 5 Jan 2003 03:51:26 GMT
Organization: cbbrowne Computing Inc
Lines: 52
Message-ID: <av8a3u$d2h2f$1@ID-125932.news.dfncis.de>
References: <pan.2003.01.03.13.58.10.249319@iprimus.com.au> <av578p$c8s17$1@ID-99293.news.dfncis.de> <av5qtf$tcf$1@lust.ihug.co.nz> <fbf82913.0301040421.1a35bdfa@posting.google.com> <3E178C63.7040901@netscape.net>
NNTP-Posting-Host: hse-mtl-ppp74247.qc.sympatico.ca (64.229.208.24)
X-Trace: fu-berlin.de 1041738686 13714511 64.229.208.24 (16 [125932])
X-Draft-From: ("nnvirtual:Linux" 1910)
X-Home-Page: http://www.cbbrowne.com/info/
X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne
X-Emacs-Acronym: Exceptionally Mediocre Algorithm for Computer Scientists
Microsoft: I'm not laughing anymore.
X-Uboat-Death-Message: ATTACKED BY AIRCRAFT. SINKING. U-567.