Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 267520

Summary:	Extreme Lag Time with Remote Workspaces
Product:	z_Archived	Reporter:	Jacob Straszynski <jacobstr>
Component:	PDT	Assignee:	Michael Spector <spektom>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	jacobstr, zulus
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Jacob Straszynski

2009-03-07 16:49:20 EST

When working with a remote workspace, that I have on a network drive, I experience extreme lag time while working with PDT.

It often happens when I copy and paste. The entire IDE freezes while it copies files across the network. 

The files that are identified are often *.dltk, and seem to be related to the content assist. In my case the file is around 3 megabytes and sometimes the ide gets into the habit of transferring it on average, every minute of use (subsequently resulting in 2 minutes of lag).

Other times, IDE will start downloading the entire project even though 'build automatically' is disabled. Something is being a bit overzealous ;)

Maybe be an Eclipse issue. Performance was much better in PDT 1.0 + Eclipse 3.3 , however.

Comment 1 Jacob Straszynski

2009-03-09 04:33:28 EDT

Note: This is not using RSE.

I'm not using RSE because RSE doesn't seem to play nice when it comes to recognizing the project I'm importing is also a CVS project.

I'm not using a local CVS repo because I like modifying the files directly to the location where they're hosted (so I can immediately demo things in my browser) - in this case, the devel server at my job.

I could achieve the same functionality with a couple of tools (local workspace, separate branch I can make private commits to when I don't want to add code to the trunk, a commit script that pushes files up to the server...) but that's a lot to get the elegance of simply using a network share.

Comment 2 Dawid Pakula

2018-07-13 10:11:49 EDT

CA is async now so shouldn't introduce lag. Other disk operations (except save) are also UI-free now.

But in general this is I/O problem outside eclipse.