Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#134245 Subversion checkouts extremely slow

First Level Support
closed
5
2009-03-28
2009-03-12
No

The vxl project has been exploring conversion to svn. However, we are experiencing extremely slow checkouts (over 1 hour in some cases).

Is this due to temporary problems with subversion services at sourceforge? I find it too slow in my experience with other subversion projects.

Thanks,
--Miguel

Discussion

    • milestone: --> First Level Support
    • assigned_to: nobody --> hinojosa
    • status: open --> pending
     
  • Hi Miguel,

    Can you please provide some more data on this issue. Are you authenticated when attempting these operations? Which specific operation are you noticing that appears to be slow?

    If you need anything else, please post a response to this request.

    Cheers!,

    Daniel Hinojosa - Sr. Manager, SourceForge.net Support

    P.S., Support items set to status of 'Pending', will auto-close in 14 days if there is no response. Be sure to monitor our Site Status page, https://sourceforge.net/sitestatus.

     
    • status: pending --> open
     
  • Hi Miguel,

    We tried this and were able to checkout the vxl repository locally at 2.4 MB/s. It's 6.7 GB with 280901 files and took 45 minutes. I don't know that there is much we can do to speed this up. The problem is that it's a bunch of small files and all those transactions add latency.

    You could try checking out just the part of the repository you need to work on so you don't have to check out the whole thing.

    Best regards,

    Daniel Hinojosa - Sr. Manager, SourceForge.net Support

    P.S., Support items set to status of 'Pending', will auto-close in 14 days if there is no response. Be sure to monitor our Site Status page, https://sourceforge.net/sitestatus.

     
    • status: open --> pending
     
    • status: pending --> closed
     
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).