[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=12992235#comment-12992235 ] 

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

Infrastructure related:
- dedicated server only for performance tests
- tools : perftest (https://github.com/vpakan/perftest), reddeer for UI actions


About actual tests:
We are testing two things right now:

1. Import projects (javaee 6, richfaces, html5 from central and ticketmonster) with different .project files to enable only validators we want:
- No validation is performed
- JDT validation
- WST validation
- Hibernate validation
- CDI Validation
- JST Validation

We always add validation on top of previous

2. Import big project - wildfly.

We disabled maven for all projects (did Materialize library on all of them) to minimize network issues. 

Results can be seen here http://perflin64.mw.lab.eng.brq.redhat.com:8180/PerfServer/faces/testsuites.xhtml?projectid=3 

You can also compare two runs there, but results for the same actions on the same machine and same JBDS build differ sometimes quite a bit.


> 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
>      Security Level: Public(Everyone can see) 
>          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.2.6#6264)