Admin: HTTP Proxy Cache
From Resin 3.0
(Difference between revisions)
(New page: Category: Admin Category: Cache When you want to increase performance, one of the easiest and most effective techniques is to use Resin's proxy cache and improve the ratio of page...) |
|||
| Line 13: | Line 13: | ||
; invocation cache miss ratio | ; invocation cache miss ratio | ||
: Counts the invocation misses, which is when Resin must calculate rewrite, servlet and filter dispatching for splitting apart the URL | : Counts the invocation misses, which is when Resin must calculate rewrite, servlet and filter dispatching for splitting apart the URL | ||
| + | |||
| + | [[Image:Cache-overview.png]] | ||
Revision as of 18:28, 5 October 2010
When you want to increase performance, one of the easiest and most effective techniques is to use Resin's proxy cache and improve the ratio of pages using that cache. A page request that avoids any database access or framework processing is a pure win for performance and latency. The proxy cache can be particularly effective in combination with load balancing because Resin's proxy cache can save load on the web-tier server itself.
Summary
You can use the summary page to get an overview of the cache effectiveness by looking at the miss ratio of the proxy cache and block cache. The lower the miss ratio, the fewer requests that take up database and framework load. Each "miss" is a request that goes through the full processing of a page.
- proxy cache miss ratio
- The percentage of requests that miss the caching, going on to full processing.
- block cache miss ratio
- The underlying disk reads and writes ("block reads/writes") paging from memory caching to disk caching.
- invocation cache miss ratio
- Counts the invocation misses, which is when Resin must calculate rewrite, servlet and filter dispatching for splitting apart the URL
