StarTeam plug-in for Eclipse is awfully slow
From: Ralf Jonas (scraponly_at_hotmail.com)
Date: 03/10/04
- Next message: Davor Cengija: "Re: JUnit in Eclipse - how to write to log file?"
- Previous message: Horst Walter: "JUnit in Eclipse - how to write to log file?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 10 Mar 2004 13:13:29 +0100
Hi,
for our current JAVA project we use Eclipse 2.1.2 and a stand-alone StarTeam
5.2 client for Windows. This works very fine and quite performant. Our
developer workstations are Pentium4 2.4 GHz with 1 MB RAM and Windows XP
installed. But since we cannot switch from an editor window containing a
class with an error diretly to the corresponding file in StarTeam we
searched for a plug-in.
But now we tried the StarTeam plug-in for Eclipse Version 5.3.0 and after
several hours of using we all are fed up with that: It works and we got all
functions and gimmicks we asked for. But it's terrible slow, even changing
from one editor window to another takes minutes, not to speak from checking
out or checking in. Opening a window with all project files (approx. 2500)
takes several minutes whereas the stand alone client takes only some seconds
to do the same.
The windows task manager reports about 200 MB of free physical memory, so
where is the problem? Are there any hints we don't know? We only need the
"Files" section from StarTeam, nothing else. We need to check-in and to
check-out files properly locked and we need to updated our local source with
out-of-date files from the repository or to delete source which is
Not-In-View.
Thanks in advance for any hints
Ralf Jonas
- Next message: Davor Cengija: "Re: JUnit in Eclipse - how to write to log file?"
- Previous message: Horst Walter: "JUnit in Eclipse - how to write to log file?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
