[
https://issues.apache.org/jira/browse/ARTEMIS-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032693#comment-16032693
]
ASF GitHub Bot commented on ARTEMIS-1185:
-----------------------------------------
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1295
@clebertsuconic It is something I think can over-complicate the environment
setting for a user and could potentially makes the mechanism less efficient too.
That's why:
- the file is not a "real" file on Linux (it uses
[/dev/shm](https://www.cyberciti.biz/tips/what-is-devshm-and-its-practical-usage.html))
to avoid potential costs on page swapping/writeback of the dirty region, hence
the position/name could not be bound to a fixed configured position
- the file need to be zeroed on broker start and to make this behaviour
safer&simpler to be implemented I prefer to let the file system do it for me,
creating a new file with `pid-date of creation` info on the name (+
File::deleteOnExit), hence a fixed file name is not an option here too
wdyt?
> 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)
