[jbosstools-issues] [JBoss JIRA] (JBDS-2948) Importing small or large projects with many dependencies should not be slow

[Max Rydahl Andersen (JIRA)]

     [ https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBDS-2948:
--------------------------------------

    Description: 


Users have had noticable issues when importing projects having many schemas, many annotations and dependencies in past. Our and WTP validators seem to be causing issues - some are actual performance issues and others seem to be more perceived than actual issues.

Unfortunately perceived issues for the user feels just as slow as real issues.

Suggestion:

    Look in jira for performance issues and add "performance" label to them

    Allocate dev to use profiler to spot hotspots and get these findings reported/documented and then triage based on these findings

    Work with QE to setup performance measurements for end user common operations related to these issues (example: import project, run validation etc.) for small (quickstarts), medium (ticketmonster) and large (wildfly) projects and publish these numbers over time and keep track if getting better/worse.

    Setup goals to reach for these performance measurements.

    Don’t add new features that make performance worse. For example don’t introduce one more slow validation feature to the validator which already has performance issues until those issues are solved.



    
> Importing small or large projects with many dependencies should not be slow
> ---------------------------------------------------------------------------
>
>                 Key: JBDS-2948
>                 URL: https://issues.jboss.org/browse/JBDS-2948
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Epic
>      Security Level: Public(Everyone can see) 
>            Reporter: Max Rydahl Andersen
>
> Users have had noticable issues when importing projects having many schemas, many annotations and dependencies in past. Our and WTP validators seem to be causing issues - some are actual performance issues and others seem to be more perceived than actual issues.
> Unfortunately perceived issues for the user feels just as slow as real issues.
> Suggestion:
>     Look in jira for performance issues and add "performance" label to them
>     Allocate dev to use profiler to spot hotspots and get these findings reported/documented and then triage based on these findings
>     Work with QE to setup performance measurements for end user common operations related to these issues (example: import project, run validation etc.) for small (quickstarts), medium (ticketmonster) and large (wildfly) projects and publish these numbers over time and keep track if getting better/worse.
>     Setup goals to reach for these performance measurements.
>     Don’t add new features that make performance worse. For example don’t introduce one more slow validation feature to the validator which already has performance issues until those issues are solved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira