ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35852] New: - Speed up th e StarTeam checkout task
Date Mon, 25 Jul 2005 17:18:38 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35852>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35852

           Summary: Speed up th e StarTeam checkout task
           Product: Ant
           Version: 1.7Alpha (nightly)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: Optional SCM tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: BBurgess@tiaa-cref.org


I have come up with some changes to be made which will more than double the
speed of the StarTeam checkout task.  I have tested them and our company has
been using these changes currently for the last 4 weeks now with complete success.

The current stcheckout task takes about 4 units of time for every single file
checked out.  The value of these units of time depends on your StarTeam server
setup (for us here, each unit of time is 1 second).  For every single file
checked out, the following occurs: 

1) (one unit of time) - Fetch the encoding property for the file

2) (two units of time) - Perform the checkout

3) (one unit of time) - Update the local cache with the files new status

Both steps 1 and 3 can be removed safely.

An unforced checkout is used by developers on their local machines in order to
make sure they have the latest code that has been checked in by any other team
members.  It will only checkout the files whose status is OUTOFDATE or MISSING.
 However any files whose status is reported as MODIFIED or MERGE or UNKNOWN will
not be checked out as this could overwrite local work that has been done on the
files.  Also, files with the CURRENT status will not be checked out as the local
version is an exact copy of what's in the server (so re-checking out an exact
copy of what you already have is silly and a huge waste of time).

A forced checkout is used by automated scripts on build machines and servers in
order to sync the local folder with what is on the server.
Therefore files are checked out regardless of their status.  The problem is that
even files with the Status CURRENT are checked out.  In a continuous build
scenario using forced checkouts, 90% or more of the time spent to checkout a
project is wasted on re-checking out files that are already CURRENT.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message