Article View: comp.sys.mac.oop.macapp3
Article #226Re: RAM cache /Rapid Track
From: Tandem, Gary Campbell,PAS
Date: Wed, 06 Jan 1993 04:57
Date: Wed, 06 Jan 1993 04:57
85 lines
3219 bytes
3219 bytes
Hi David,
I have been experimenting with Insigna Solution's Rapid Trak
ram cache/disk driver for the last two weeks to compile my large
C++ MacApp 3.0.1 appilcation.
It is a combination disk driver and ram cache, it must be installed
by reformatting your hard disk with their driver to operate.
It costs about $99 LIST, $66 mailorder US.
My Application takes 20 minutes to compile and link on a 20 mb
50mh 60030 Daystar.
The CPlus dump file is 2.8 mb,
the .SYM file is 1.7 mb, and
the application is .8 mb
The size of these files have been a problem trying to use RAMDISKs and
this ram cache because they are larger than the amount of ram I have
left over in my 20mb system( LINK uses ~8-9 MB ).
What I used to do was use every trick in Kent's tech note and then the
following,
I modified MA's build rules and dependencies move MacApp.lib to
my RAMDISK before the LINK, and build the application's object
on the ram disk.
Also on the ramdisk were the CPlusScratch, MABUILD.temp files.
After the LINK was over I duplicated the Application back to disk
and purged MacApp.lib.
I was basically trying to get the "hotest" files on a 6mb ram disk since
I didn't have enough room to put every thing there.
The compile and link time for 1 file( not the entire set ) was:
230 secs ( includes use a CPLUS -load file and duplicating the
files between ram disk ).
With Rapid Trak set to 3.5 mb, ( which my sources just barely fit in )
and using a .5mb ram disk for the CPlusScratch file, and not running the
2.8 mb CPlus load file through Rapid Trak,
the compile and link time is the same,
230 secs,
This isn't a elapsed time improvement, but becomes an improvement when
I rebuild more than one file because they use common ".h" files and the
hit rate becomes 80-90% during the compiles.
But it is an overall improvement because,
o I get an improvement on more than one file rebuilt
o Object Master's search function ( cmd L ) runs like a bat out of hhhh
The drawbacks to RapidTrak are minor so far,
1 It works well with my SyQuest 88
2 And MPW
3 And MacApp
4 And The Debugger
The drawback is,
1 It only allows a 4 mb ram cache ( fine with me but maybe not
for 32 mb machines )
2 I haven't tested the formatters capability to reformat
bad tracks which non-sealed SyQuest cartidges encounter from
time to time.
I can live with those
3 I had a couple of flakes with a 3 mb Rapid Track setting and doing
a CPlus -loadc on my 2.8 mb dump file. I finally moved the
dump file to a drive not with a Rapid trak cache.
cheers,
Gary Campbell
Tandem Computers
Technical Details
Message-ID:
<726296939.7547114@AppleLink.Apple.COM>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!cs.utexas.edu!sun-barr!olivea!apple!applelink.apple.comShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!usc!cs.utexas.edu!sun-barr!olivea!apple!applelink.apple.com From: V0645@AppleLink.Apple.COM (Tandem, Gary Campbell,PAS) Newsgroups: comp.sys.mac.oop.macapp3 Subject: Re: RAM cache /Rapid Track Message-ID: <726296939.7547114@AppleLink.Apple.COM> Date: 6 Jan 93 04:57:00 GMT Sender: daemon@Apple.COM Organization: AppleLink Gateway Lines: 85