#60 Better ns_cache statistics

Feature Request
closed
1
2006-12-01
2006-02-08
No

(Posted on behalf of Gustaf Neumann by vasiljevic)

Determining a good cache size and useful
time-out-values is a non-trivial task.
ns_cache_stats returns already some useful
statistics, but i would say, at least two
important figures are missing, which are
subsumed by the # of flushes. Actually,
there are at least 3 kind of flushes:

a) expires (entry is too old)

b) prunes (entry thrown out of the
cache due to space competition)

c) intentional flushes (flush command,
deletion of an entry, etc.)

Currently, nscache lumbs a+b+c under flushes.
It would be nice to obtain separate values
for these kinds of flushes to get some idea,
whether or not a cache behaves like expected,
or whethe it should be increased or decreased.

Discussion

  • Zoran Vasiljevic

    • status: open --> closed
     
  • Zoran Vasiljevic

    Logged In: YES
    user_id=95086

    Done in cvs head. The ns_cache_stats return following data:
    maxsize X size X entries X flushed X hits X missed X hitrate X expired X
    pruned 0

    New elements are: "pruned" and "expired"

    "pruned" counts number of entries removed from the cache because of the
    cache-size constraint

    "expired" counts number of entries removed from the cache because of the
    time-to-live constraint

     
  • Stephen

    Stephen - 2006-12-01
    • labels: 711757 -->
     
  • Stephen

    Stephen - 2006-12-01
    • labels: --> NaviServer - libnsd, libnsthread, nsd
    • milestone: --> Feature Request
    • priority: 5 --> 1
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks