We have an application that requires a large cache (> 100MB) capable of storing many thousands of 1 kB files for quick look-up read access. To maximize performance, its highly desirable that all entries, once cached, remain local to the client so that ultimately, the number of cached entries (-dcache) would equal the number of available cache files (-files). The problem we have in configuring a large cache comprised of many small files is that cache size, measured in number of stored files, seems be software-limited to an upper bound of 32k files. That means the largest cache our application can use is limited by (32k files) x (1kB/file) = 32MB. We'd like to be able to store about 200MB worth of 1kB files on a local AFS cache, to function as a fast look-up server, but the current implementation of afsd prevents this scale of cache management. Is the 32k limit on the number of cache files permitted by afsd something that can be changed--or something that could possibly be changed in a future AFS release? Thanks, Bob Dew National Institutes of Health Bethesda, MD
