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 Wed, 31 May 2017 13:41:05 GMT

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

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

Github user clebertsuconic commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1295
  
    ``Currently the user running the sampler could choose where put the trace recorded from
the profiler using the --out parameter:``
    
    There's an option on the configuration. I think it's logRates.. something like that...
if you used the config for that, you won't have to configure the --out.


> 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)

Mime
View raw message