Article View: comp.sys.transputer
Article #1873On-chip Ram: Helios, D7205
From: Mauricio Gomez Calderon
Date: Thu, 07 Jan 1993 20:02
Date: Thu, 07 Jan 1993 20:02
49 lines
1766 bytes
1766 bytes
Hi Again...
I was testing the on-chip RAM for a single Transputer:
In Helios, i tried to accelerate a small test routine, using the
fast on-chip Ram memory. The code is as follows:
void cycle(int iterations) {
int i;
for(i=0; i<iterations; i++) {
/* nothing! */
}
}
In a normal situation, this takes 14 sec for 10,000,000 iterations.
Using on-chip Ram, this takes 6 sec for 10,000,000 iterations.
But in D7205 Occam 2 Toolset, if i try to do the same...
VAL INT iterations IS 10000000:
SEQ
clock ? time1
i := 0
WHILE ( i < iterations )
SEQ
-- nothing!
i := i + 1
clock ? time2
In a normal situation, this takes 10 sec for 10,000,000 iterations.
Using order.code := -1 in the .pgm this takes 14 sec for the same iterations.
I suppose that this occurs because the occonf try to optimize by default
the use of the on-chip RAM for small routines...
But what about the best times? 6 sec in Helios and 10 sec in D7205 for the
almost 'same' application... Furthermore, the occam process is the only
process in the transputer...
Why this difference? Thanks in Advance...
Maurro
Technical Details
Message-ID:
<1993Jan07.200247.37029@dcc.uchile.cl>Path:
arc1-ca.pugleaf.net!sparky!uunet!uchdcc!inti!maurroShow Full Headers
Complete Article Headers
Newsgroups: comp.sys.transputer Path: arc1-ca.pugleaf.net!sparky!uunet!uchdcc!inti!maurro From: maurro@inf.utfsm.cl (Mauricio Gomez Calderon) Subject: On-chip Ram: Helios, D7205 Sender: usenet@dcc.uchile.cl (Network News) Message-ID: <1993Jan07.200247.37029@dcc.uchile.cl> Date: Thu, 07 Jan 1993 20:02:47 GMT Nntp-Posting-Host: inti.inf.utfsm.cl Organization: Informatica UTFSM X-Newsreader: TIN [version 1.1 PL8] Lines: 50