[
https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2948:
-------------------------------------------
disabling Maven I believe is a bad idea since its probably one of the areas we need to
identify the issue.
if network issue is the problem why not just have a pre-seeded ~/.m2-custom repository
used in test ? Then you dont get the network latency but can test the maven impact ?
I tried browsing
http://perflin64.mw.lab.eng.brq.redhat.com:8180/PerfServer/faces/testsuit...
but could not grok it ..or all tests failed ?
...is there a way to run these tests locally without having to setup a server etc ?
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.3.1#6329)