activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1185) Inter-Process Journal Sampler Profiler + CLI command
Date Thu, 29 Jun 2017 22:15:00 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069087#comment-16069087
] 

ASF GitHub Bot commented on ARTEMIS-1185:
-----------------------------------------

Github user franz1981 commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1295
  
    @clebertsuconic Maybe I've not understand your comment...but to capture data I use lock-free
inter process communication primitives,hence no lock is involved because locks works only
in the same process.
    Please look at the MultiSampleBuffer implementstion: it is the core of the whole process.


> Inter-Process Journal Sampler Profiler + CLI command
> ----------------------------------------------------
>
>                 Key: ARTEMIS-1185
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1185
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Minor
>
> It provides a sampling profiler on buffered ASYNCIO/NIO based journals.
> The profiling has a minimal cost in term of CPU time for each sample (the dominant costs
are System.nanoTime() and a single cache line invalidation) and total memory footprint (~OS
page size in bytes).
> A proper CLI command activates a sampler to collect (ie CSV) the profiled data, showing
the precision of the sampling: data loss is not considered a failure condition.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message