>From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] >
<skip/> > >Everytime a request comes, I have the information on the 'estimated' >time the resource will need to be generated on the different routes. >Once the decision is taken, I have the information on how much it took >to get it and I can compare it with the "assumed" time that would have >taken on the other path. Then I know how much time I *saved* with this >choice. > >But we don't stop here: we also have a way to measure the efficiency of >the cache itself between cache hits and cache misses. > >This information might be used to estimate the RAM a server would >require to obtain near-maximum efficiency. > >And all this without even touching a single configuration!!! > >A wonderful example of the advancement of adaptivity on caching is that >you have an immediate feedback (with numbers!!!) on how much a change, >say, in your database monitoring code, influences caching efficiency. > >This is a completely innovative approach because the decision whether or >not to cache something is estimated a-priori by system administrators, >but in complex systems, very few people can make this decision and tune >it for every change in the system. > >Consider this as a hotspot caching machine. Berin, you introduced some days ago a Profiler in Avalon Excalibur. Is that Component designed to handle such things? Gerhard (still trying to get the big picture of caching) ------------------------------------------- Beer is God's way of showing us he loves us and wants us to be happy... ------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
