felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre De Rop (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-4667) "top" command for the Dependency Manager Shell
Date Tue, 07 Oct 2014 20:36:33 GMT

     [ https://issues.apache.org/jira/browse/FELIX-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Pierre De Rop resolved FELIX-4667.
    Resolution: Fixed

committed a simple patch rv  1629978, which implements this new shell command.

> "top" command for the Dependency Manager Shell
> ----------------------------------------------
>                 Key: FELIX-4667
>                 URL: https://issues.apache.org/jira/browse/FELIX-4667
>             Project: Felix
>          Issue Type: Improvement
>          Components: Dependency Manager
>            Reporter: Pierre De Rop
>            Assignee: Pierre De Rop
>            Priority: Minor
>             Fix For: dependencymanager-4.0.0, dependencymanager.shell-4.0.0
> This issue proposes to add a new simple "top" option to the Dependency Manager Shell
in order to list all the "top components", sorted by their "start" lifecycle callback duration
> This command would then be very helpful in order to figure out what are the most expensive
components, taking some long time in their start method.
> For example, the following gogo command allows to dump the top 2 components class name
having the most expensive start duration time. The list is sorted by the start duration time,
and the init/start time are displayed in nano seconds:
> {code}
> dm top 2
> g! dm top 2
> Top components (sorted by start duration time)                    [init time] [start
> -------------------------------------------------------------------------------------------------------
> foo.bar.BigComponent                                                            91371
> foo.bar.AnotherBigComponent                                               156563    4493985
> {code}

This message was sent by Atlassian JIRA

View raw message