4 ms·
We’d be interested in hearing more about your situation, so that we can further improve Reposurgeon. If you can profile it as it reads your svn dump (using the
by db48x 5y ago
We’d be interested in hearing more about your situation, so that we can further improve Reposurgeon. If you can profile it as it reads your svn dump (using the `profile start` and `profile save` commands), it could really help us out.
How many commits does your repository have? The largest one we’ve successfully converted from SVN to Git ourselves was 287k commits.
- danudey 5y agoSorry for the late reply, but: 1. I'll try doing some profiling and see what happens 2. The latest repository I tried to import has 671,190 revisions
- db48x 5y agoWow. That is a huge repository. You can also force it to write all file content (blobs) out to temporary files rather than keeping them in memory by reading the stream from standard input: reposurgeon "read -" … <dump.svn That will be slower and use more disk space, but maybe it will fit.
- danudey 5y agoThanks for the suggestions, I'll give that a try! And yes, some of our repositories are huge. This one is about 240 GB, and comprises multiple projects/products. Our "most important" repository is only 313,000 revisions, but those revisions take up 93 GB, so it's a not-insubstantial repository as well.