Hi,
yes the metrics will affect performance. nothing we can do about that
really (except trying to keep it as small as possible). Which is why the
metrics should always be a feature that can be turned on only when you
need to see how your app is doing at the moment, tweak it, and turn it
off.
On Mon, 4 Dec 2000, Bordet, Simone wrote:
> Very interesting. How do you suggest to write such a thing for the cache ?
> There is any problem to send zillion messages, as cache activity can be
> really high (for example in benchmarks).
well I wouldnt turn the metrics on for benchmarks (it isn't really suited
for that). For "normal" usage, I'd expect a graph of the cache size to be
useful, and how it varies during different time periods and under
different loads, etc. Something you can sample quite infrequently
(when measuring in milliseconds).
The metricsinterceptor itself sends a message with each method call which
is rather extreme and certainly something you wouldn't keep around for
long periods of time in a production environment. Same thing goes for
caches.
> Will this be something like this ?
> add a topic in Spyder and register it on JNDI
> every time the cache does something interesting, send a message to this
> topic (or maybe subtopics)
yep, when you init cache, get topic from JNDI, register as a publisher to
that topic, when say, cache is resized, send off a msg.
> How will it impact on cache performance ?
metrics always has overhead.
> Does all the messages are kept by the topic or they're cleaned after a while
> ?
Depends on the topic settings: PERSISTENT/NON-PERSISTENT and the publisher
can set time-to-live value.
-- Juha
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
