[
https://issues.apache.org/jira/browse/LOG4J2-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133445#comment-14133445
]
Remko Popma commented on LOG4J2-753:
------------------------------------
Because on Linux systemClock was 220x slower than on Windows in a [previous
benchmark|https://issues.apache.org/jira/browse/LOG4J2-744?focusedCommentId=14077425&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14077425].
I'll run the benchmark again on Solaris and Linux at work next week. If
cachedClock is not faster than systemClock in those environments I'll remove it.
> CachedClock performs badly when contended by many threads
> ---------------------------------------------------------
>
> Key: LOG4J2-753
> URL: https://issues.apache.org/jira/browse/LOG4J2-753
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0
> Reporter: Remko Popma
> Assignee: Remko Popma
> Fix For: 2.1
>
>
> See LOG4J2-744 comments for JMH benchmarks highlighting the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
