[news.eclipse.tools.pdt] Re: PDT 2.0.0GA unusably slow

["Michael Spector" <michael@xxxxxxxx>]

Hi,

Can I ask everyone who's experiencing issues when working on remote drives 
to enable the following preference:

Window->Preferences->Dynamic Languages->File Caching (choose: Default File 
Caching).


This option should improve performance when working on files stored remotely 
either via shared folder or using RSE.

Please report about your feelings :)

Thanks!

"Dennis Verspuij" <dennis.verspuij@xxxxxxxxx> wrote in message 
news:568ec38a3801a1b07ed7cc2a9b68fc35$1@xxxxxxxxxxxxxxxxxx
> Hi Michael,
>
> Thanks for your prompt answer, I added a comment to the issue.
>
> Greetings,
>
> Dennis
>
> Michael Spector wrote:
>
>> Hi Dennis,
>
>> Yes this bug is related to your issue as well.
>> Can you add your comment to this bug?
>
>> Thanks!
>
>> "Dennis Verspuij" <dennis.verspuij@xxxxxxxxx> wrote in message 
>> news:44d55f4a69af8c1e309c585dc495d9a7$1@xxxxxxxxxxxxxxxxxx
>>> Hello, I just installed latest PDT 2.0.0GA from the all-in-one download. 
>>> I added an existing large PHP project to the workspace. The project uses 
>>> the Symfony framework, so I added the framework to the build path in 
>>> order to have code assist etc. Furthermore I installed Subclipse 1.4.7, 
>>> Mylyn 3.0.3 with Trac connector and Symfoclipse 1.2.1 for its yml 
>>> editor. The project is located on a Samba network drive.
>>>
>>> My problem is that PDT is extremely slow in (re)building, e.g. it takes 
>>> up to 15 minutes to complete with 10% average CPU consumption. During 
>>> the period PDT cannot be used. The same happens every now and then while 
>>> editing a PHP file (for example inserting a dollar sign ($)) and PDT 
>>> attempts to show some code completion/assist possibilities. I might turn 
>>> the latter features off, but it's PDT I want to use for that in the 
>>> first place. I used PDT 1.0.3. before and it was much faster even tough 
>>> it had to rebuild a project every time.
>>>
>>> Does anyone experience these problems as well or have have suggestions 
>>> to fix this? I noticed bug 259788 
>>> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=259788), can this be 
>>> related?
>>>
>>>
>
>
>