On Apr 9, 10:21 am, Eric Bergen <[email protected]> wrote: > Trending the data over time is better left to other tools that trend data > over time. The memcached stats should be a snapshot in time that other tools > can consume. If you start trending things in memcached you not only waste > resources but you will end up with metrics like unix load average that are > meaningless because they can't be directly compared to anything else.
We're not talking about trending in the server, we're talking about a ``current'' value (e.g. how many clients are currently connected to my server) vs. ``rate'' values (e.g. how many connections have there ever been, which can be trended). You don't have to pick one. You *could* just increment both adds and removes separately and compute the point-in-time. If a size_t counter ever wraps, that becomes...quite difficult, though.
