On 07/23/2010 05:12 PM, Mark Phippard wrote:
> Listeners are called when files are modified. So things like saving files or doing updates, when builds get triggered, should be smoother.
The "refreshing references" wait? It might be slightly faster. If not,
well it's working, so I'm happy.
I'm using Google Web Toolkit & Perl, so I'm not sure how the "... builds
get triggered..." applies. I'm sure that there's an Eclipse refresh
phase when starting a GWT compile, but I've never seen an
Eclipse-generated stall.
> On Jul 23, 2010, at 8:01 PM, JChimene <jchimene_at_gmail.com> wrote:
>
>> On 07/23/2010 02:11 PM, Mark Phippard wrote:
>>> We have been doing some overhaul on some of the internals of
>>> Subclipse, particularly in the area of our resource change listeners.
>>> These are what get called by Eclipse whenever something is modified.
>>> We use them for a lot of purposes and the performance of this code is
>>> critical to overall Eclipse performance as they can cause other
>>> Eclipse code to be stuck waiting for them to finish.
>>>
>>> I would like to get more people trying the code before we put out an
>>> official new release. The changes seem to make Eclipse much faster
>>> and we have not observed any regressions caused by the change. I have
>>> posted dev builds to our CollabNet Desktop update site. The current
>>> version is 1.6.12.2. You can get the URL's for the update sites here:
>>>
>>> http://desktop-eclipse.open.collab.net/servlets/ProjectProcess?pageID=3794
>>>
>>> If you are only installing Subclipse, it does not matter which site
>>> you use. There are only multiple sites, because we host the Mylyn
>>> downloads on these sites, and they have different code for different
>>> Eclipse versions.
>>>
>>> Once we get some feedback that there are no new problems (and ideally
>>> hear confirmation that Eclipse feels faster) we can do a Subclipse
>>> 1.6.13 release and post it to the normal update site.
>>>
>>> Please try this release and provide feedback.
>>
>> Hi Mark:
>>
>> I just installed it for Eclipse 3.6
>>
>> In the absence of any specific subclipse operation suggestions, I closed
>> and reopened my current project.
>>
>> The close time seems faster.
>>
>> The open time seems about the same.
>>
>> I've never had a problem with the time it takes to do a version compare
>> or a commit.
>>
>> Are there other subclipse tasks that might be appropriate to try?
>>
>> ------------------------------------------------------
>> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2637494
>>
>> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
>
> ------------------------------------------------------
> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2637498
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2637503
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2010-07-24 02:40:27 CEST