ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (IVY-655) Ease performance auditing
Date Wed, 05 Dec 2007 22:03:44 GMT

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

Xavier Hanin resolved IVY-655.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-beta-1

I've committed (yesterday actually) a few modifications making auditing performance easier:
- a new log trigger, which is roughly equivalent to the echo task from ant, but not relying
on ant as ant-build and ant-call triggers, making it better performing and thus better suited
for performance tracking
- added some performance metrics in some events, like post-resolve, post-download, ...
- added events for retrieve as well, to audit performance of this operation too
- slight update of the default console output, to add some basic time information

> Ease performance auditing 
> --------------------------
>
>                 Key: IVY-655
>                 URL: https://issues.apache.org/jira/browse/IVY-655
>             Project: Ivy
>          Issue Type: Improvement
>            Reporter: Xavier Hanin
>            Assignee: Xavier Hanin
>             Fix For: 2.0.0-beta-1
>
>
> Ivy currently provides some performance metrics (size and time when downloading a file),
but their location in the log make it difficult to use. On the other hand, the trigger mechanism
can be used to track how things are performed, but is lacking basic performance information
such as the download time. Improving the events triggered during the resolution process with
more performance related metrics would help to investigate performance issues and improve
Ivy setup.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message