[jira] [Commented] (ARTEMIS-1185) Inter-Process Journal Sampler Profiler + CLI command

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user franz1981 opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1295

    ARTEMIS-1185 Inter-Process Journal Sampler Profiler + CLI command

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/franz1981/activemq-artemis real_time_journal_latency

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1295.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1295
    
----
commit 87b59431dbab8d987d217bb9bcdaac688bd5f120
Author: Francesco Nigro <ni...@gmail.com>
Date:   2017-05-17T08:35:35Z

    ARTEMIS-1185 Inter-Process Journal Sampler Profiler + CLI command

----


> 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.3.15#6346)