[jira] Closed: (SCM-65) should use compression when getting log

["Emmanuel Venisse (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/SCM-65?page=all ]
     
Emmanuel Venisse closed SCM-65:
-------------------------------

      Assign To: Emmanuel Venisse
     Resolution: Fixed
    Fix Version: 1.0-beta-1

Done.

> should use compression when getting log
> ---------------------------------------
>
>          Key: SCM-65
>          URL: http://jira.codehaus.org/browse/SCM-65
>      Project: Maven SCM
>         Type: Bug
>   Components: maven-scm-provider-cvs
>     Versions: 1.0-alpha-4
>  Environment: WinXP
> Client: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build 2115 (client/server)
> Server: Concurrent Versions System (CVSNT) 2.0.34 (client/server)
>     Reporter: Brian Ewins
>     Assignee: Emmanuel Venisse
>      Fix For: 1.0-beta-1

>
>
> Continuum uses SCM to grab the logs hourly, if there are any updates - which is pretty much always on any active project. On our project, this takes 1m 55s for a 16Mb download. While logs are being downloaded, the repository is locked (this may be a CVSNT issue only). So, for 2 mins an hour, no-one can do commits. This is a large enough chunk of time that it causes complaints.
> While continuum could ask for a smaller chunk of the log, the biggest difference is made by using the -z3 flag to compress it. Timing that in our situation it takes only 15 seconds to download the log, which is much more acceptable. 
> the fix is to change CvsChangeLogCommand to read :
> ...
>         Commandline cl = new Commandline();
>         cl.setExecutable( "cvs" );
>         cl.setWorkingDirectory( fileSet.getBasedir().getAbsolutePath() );
> +      cl.createArgument().setValue( "-z3" ); // use compression
>         cl.createArgument().setValue( "-f" ); // don't use ~/.cvsrc
>         cl.createArgument().setValue( "-d" );
> ...
> of course this may have consequences on other cvs implementations; but having some way of configuring this would make it usable.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira