Schoeberl, Martin Huber, Benedikt Puffitsch, Wolfgang We estimate that adding name and attribute caching to the Sprite operating system could reduce server load by 36 percent and the number of network packets by 30 percent.ĭata cache organization for accurate timing analysis Caching was less successful in heavily shared and modified directories such as /tmp, but there weren't enough references to /tmp overall to affect the results significantly. Process migration to remote machines had little effect on caching. The simulations show that maintaining cache consistency between machines is not a significant problem only 1 in 400 name component look ups required invalidation of a remotely cached entry.

File attribute caching obtained a 90 percent hit rate with a cache on each machine of the attributes for 30 files. Entry-based name caches (holding individual directory entries) had poorer performance for several reasons, resulting in a maximum hit rate of about 83 percent. Caching was found to be advantageous: a cache on each client containing just 10 directories had a 91 percent hit rate on name look ups. The simulation used trace data gathered on a network of about 40 workstations. This paper presents the results of simulating file name and attribute caching on client machines in a distributed file system. Most benchmarks show a good hit rate for a method cache size in the range between 4 and 16 KB.Ī trace-driven analysis of name and attribute caching in a distributed system We evaluate the method cache with a large set of embedded benchmarks. in the time-predictable processor Patmos. The method cache caches whole methods (or functions) and simplifies worst-case execution time analysis. This paper presents a method cache as a time-predictable solution for instruction caching. Degasperi, Philipp Hepp, Stefan Puffitsch, Wolfgangįor real-time systems we need time-predictable processors.

Integrity plus realty dave nedley