We found out that our check out and diff features for M18 are fast for git but really slow for svn. The reason is that using the VCS URLs and SVN these queries will go over the network to the SVN server. Some of our queries are very detailed and look back in time. The server takes a long time to answer these queries and the data is large so throughput over the network is also a bottleneck.
We could consider two options:
- dumping the SVN repository and mirroring it locally on the OSSMETER server side
- using git svn to mirror the repository as a git repository
The second option sounds preferable, since it puts the burden of understanding SVN's model to the svn git feature , which many people already use.
Your thoughts are welcome
Discussion
-
Jurgen vinju
2014-04-01- Description has changed:
Diff:
--- old +++ new @@ -1,8 +1,9 @@ We found out that our check out and diff features for M18 are fast for git but really slow for svn. The reason is that using the VCS URLs and SVN these queries will go over the network to the SVN server. Some of our queries are very detailed and look back in time. The server takes a long time to answer these queries and the data is large so throughput over the network is also a bottleneck. We could consider two options: -* dumping the SVN repository and mirroring it locally on the OSSMETER server side -* using git svn to mirror the repository as a git repository + + * dumping the SVN repository and mirroring it locally on the OSSMETER server side + * using git svn to mirror the repository as a git repository The second option sounds preferable, since it puts the burden of understanding SVN's model to the svn git feature , which many people already use.
