Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hp-pcd!hplsla!andyc From: andyc@hplsla.HP.COM (Andy Cassino) Newsgroups: comp.sys.atari.st.tech Subject: Re: Quien es mas macho? (HD caching) Message-ID: <13510003@hplsla.HP.COM> Date: 29 Oct 90 23:14:18 GMT References: <1990Oct27.162723.2834@doe.utoronto.ca> Organization: HP Lake Stevens, WA Lines: 31 david@doe.utoronto.ca (David Megginson) asks: | | Now, how should I set up caching for the best effect under TOS 1.4? | I have turned off write caching in the ICDBOOT driver (it scares | the dung out of me), but I have to choose among using only | Atari's CACHEnnn.PRG (which is _very_ fast), ICDBOOT's built-in | read caching, or some combination of the two. Any suggestions? Is | CACHEnnn.PRG safe to use with ICDBOOT, or does it need AHDI? | Good questions! It will be interesting to hear what folks have to say. I use a cache mostly to speed up compiles, so that's how I test a cache. Otherwise, I'm not an expert on this topic, so if I make some erroneous statements, take it easy, ok? I find the ICDBOOT built-in cache, Atari's CACHEnnn, and the cache included with DiamondBack 2.xx to be roughly equivalent in performance for compiling. I understand that DiamondBack has special hooks into it's cache that allows for faster backups than could be obtained with the other caches. I haven't tested this. I only use the DiamondBack cache now, because it's desk accessory allows for the most convenient adjustments to the configuration, and because I can always be ready for a quick back-up. Also, the desk acc maintains some statistics so it is easier to optimize the configuration. I also like the fact that I can pick which drives will be cached. ICD's and Atari's caches will cache everything - including a RAM disk, which is pointless. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % Andy Cassino % % Hewlett-Packard - Lake Stevens Instrument Division % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%