[jbosstools-issues] [JBoss JIRA] (JBDS-2948) Improve Performance of small and large projects

[Rastislav Wagner (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999320#comment-12999320 ] 

Rastislav Wagner commented on JBDS-2948:
----------------------------------------

Ok. I can do the same with enabled maven and pre-seed repo - to see the impact of maven.

All tests passed. I cant figure out why it shows a red cross - maybe its a bug but anyways you can click on test suite (ValidationPerfTest) to see the results of particular test.  
You can also compare two test runs http://perflin64.mw.lab.eng.brq.redhat.com:8180/PerfServer/faces/view2.xhtml?projectid=3

AFAIK you wont be able to run the tests locally - you need a server & DB to be able to see the results.

> Improve Performance of small and large projects
> -----------------------------------------------
>
>                 Key: JBDS-2948
>                 URL: https://issues.jboss.org/browse/JBDS-2948
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Epic
>          Components: integration
>            Reporter: Max Rydahl Andersen
>            Assignee: Len DiMaggio
>             Fix For: 8.0.0.GA
>
>
> 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 was sent by Atlassian JIRA
(v6.3.1#6329)