Re: [Exist-development] Cache logging [was: log entries]

[Wolfgang M. <wol...@ex...>]

> It is not always convenient or even possible to use JMX on remote servers in many
> production environments, which makes your suggestion problematic.

Mmmh, I was hoping that JMX could become the central interface for
getting administrative information from the db - and to some extend
even change configuration parameters at runtime. As I understand it,
JMX provides a large number of options to use it without compromising
security. Even if I don't enable JMX, I can still use jconsole on the
same machine to get information from my running eXist.

> After the fact, how do you easily get a picture of how the caching was doing over a historical period of time?

Normally I'm only interested in the maximum cache use over a longer
period of time. As long as everything runs fine, I usually don't check
the caches. The main information the caching statistics provide is if
a certain cache can become a bottleneck under high load. The
historical development of the cache doesn't really tell me that much -
but I'm happy to learn.

> And then possibly add a configuration capability to selectively turn the
> cache logging off at runtime for those that don't want or need it. The latter is now easily
> accomplished with a simple change to a deployed log4j config file, which was not possible
> before.

Ok, but then we could also just assign a special logger to the cache
logs. I *really* prefer to have all logs going into the same log file.
Advantage: I can see all log messages in context. Having all logs in
the same file makes it easy to relate events to each other. I can
easily see what query causes an increase in memory consumption or
cache space ;-)

Wolfgang