[
https://issues.apache.org/jira/browse/OAK-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533069#comment-15533069
]
Francesco Mari commented on OAK-4561:
-------------------------------------
My general opinion about this is that most of those statistics are overkill. We
should stick with very simple counters, maybe a max or a min for some values,
rarely a (rolling implementation of) mean for some indicators. If something is
so important that needs further aggregation, we should consider either dumping
stuff to a specific logger or to setup a JMX bean. The logger can be enabled if
needs be and post-processed after the fact, the JMX bean should be fed to an
external monitoring system. Regarding {{SegmentWriter}}, which is the reason
why Commons Math ended up in Segment Tar, I guess we can limit ourselves with a
min, max and mean value of the timed values. [~mduerig], what is the bare
minimum that we need to report about the {{SegmentWriter}}? Can we do it
differently?
> Avoid embedding Apache Commons Math in Segment Tar
> --------------------------------------------------
>
> Key: OAK-4561
> URL: https://issues.apache.org/jira/browse/OAK-4561
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Francesco Mari
> Assignee: Andrei Dulceanu
> Fix For: Segment Tar 0.0.22
>
>
> Apache Commons Math is a relatively large dependency. If possible, embedding
> it should be avoided in order not to increase the size of the Segment Tar
> considerably.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
