From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,ee1e7bdc743a3545
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!feeder2.cambriumusenet.nl!feed.tweaknews.nl!194.109.133.84.MISMATCH!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!news.stack.nl!aioe.org!not-for-mail
From: tmoran@acm.org
Newsgroups: comp.lang.ada
Subject: Re: Multicore problem
Date: Wed, 10 Mar 2010 19:24:39 +0000 (UTC)
Organization: Aioe.org NNTP Server
Message-ID: <hn8rln$j9f$1@speranza.aioe.org>
References: 
 <095dc775-e214-4ccd-bf26-45ab27b3b277@s36g2000prh.googlegroups.com>
NNTP-Posting-Host: J4HSNf9Eqj44wTz1J3b8lQ.user.speranza.aioe.org
X-Complaints-To: abuse@aioe.org
X-Notice: Filtered by postfilter v. 0.8.2
X-Newsreader: Tom's custom newsreader
Xref: g2news1.google.com comp.lang.ada:9513
Date: 2010-03-10T19:24:39+00:00
List-Id: <comp.lang.ada>

>Thanks a lot to all responded. What is clear now is that the problem
>is rather complicated.
  In the early days of virtual memory, one of our users (at U of
Wisconsin) decided to make use of the large memory by declaring large
arrays, which his program accessed by running down columns.
Unfortunately, the compiler allocated them by rows, so his program's
thrashing brought the whole system to a crawl.  I imagine there will
have to be a similar learning process for using multicores well.