CompuServe Messages

That's where we disagree. My point is that since it is a file cache, large files can be cached to hard disk or RAM and get very good results. Or, you can set Speedway to ignore large files and cache small ones only. Let me give you an example. Let's say you're working a database application where the data file is huge….say 50+ Meg. The index is smaller (2Meg.). I would set Speedway to cache the index and ignore the data file. By doing this the data Speedway would grab optimizes the application. Animations are another good example. By caching the file, there is no jerkiness or pausing to the application. A track or sector cache may give some improvement, but no where near the performance gain of the file cache. IMHO, file caching is significantly faster than sector/track caching for one important reason. Our 'read ahead' can't be better than having the whole file, where a normal cache must try to guess to retrieve the correct information from the file. The GO in mammels for example improves over 1600% with Speedway. With other caches, the best improvement I could get was only 140%. In this case it's either GO in 91.2 seconds with no cache, 54.7 with Speedcache+ or 5.1 seconds with CD SPEEDWAY. I significant difference. Reese.