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

[Andrzej J. T. <an...@ch...>]

Wolfgang:

> I had a look at the statistics logging. The cache log is more or less
> worthless now. It only prints statistics for those index files which
> have not been migrated to the new index architecture yet. The memory
> log might be useful.
> 
> The cache logs should be disabled.

I disagree at the moment, but am open to having my mind changed...

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

After the fact, how do you easily get a picture of how the caching was doing over a historical period of time? Doesn't
JMX, as currently implemented in eXist, just show you the current status, not keep a historical view? Cache performance
is key to production performance with larger databases, and that typically requires historical information.

I would rather see an extension of the cache logging to support the new indexes as I believe that this would serve the
needs of production, real-world users better. 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.

Since the cache log entries no longer clutter the main exist.log file,they are now closer to being "disabled". I thought
that was a good compromise to all the opinions that were expressed, and that would have the least potential impact on
production users in the short term.

> True. My first answer was "remove the log and use JMX" and I just did
> not have time to write a second email on this issue. There are dozens
> of weeks old emails which are waiting for an answer in my inbox.

See above comments. I am not convinced that JMX alone is a good long-term solution to this.

> We start to waste too much time on questions of minor importance. To
> avoid lengthy discussion threads which allow for many interpretations,
> everyone should probably try to give short, definite answers. 

No argument there from me. ;-)

> Adam said: please use exist-development.

I have moved this thread to the dev list. Should have done so a while ago...but didn't notice it was still on open.

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com