[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| Re: [eclipse.org-architecture-council] Competition for improving the	IDE startup time | 
Improving the performance is always good
:-)
I didn't look at the test but I think
it only covers a very simple case. We would have to create test cases for
different scenarios, e.g.
- lots of open editors and views
- target platform that needs to be resolved
via network
- projects not on local disk
etc.
Of course we can also just pick one
or two most interesting scenarios for the competition (as a start). The
first round of prizes would go to the people who create official performance
tests for the selected scenarios, so that we can use the official performance
results.
Dani
From:      
 Lars Vogel <lars.vogel@xxxxxxxxxxx>
To:      
 "eclipse. org-architecture-council"
<eclipse.org-architecture-council@xxxxxxxxxxx>
Date:      
 13.07.2015 08:14
Subject:    
   [eclipse.org-architecture-council]
Competition for improving the        IDE startup
time
Sent by:    
   eclipse.org-architecture-council-bounces@xxxxxxxxxxx
Hi,
In the last release we had the Great bug initiative.
I think one great area for improvement would be the reduction
of the startup time in the IDE.
Maybe the Eclipse foundation could make a competition for
improving it? Accepted contributions could be ranked by improvement and
the largest improvements would win the price. 
For the measurement we have in platform a startup time
test, which I think could be used for the measurement. Dani, what do you
think?
If we would do this, we should get the buy-in from the
involved projects. For platform Dani would have to say yes, for p2 Pascal,
etc.
Best regards, Lars_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.