This seems to be solved. Well past the troublesome revision after about
10 hours and 70GB of virtual memory.
On 27/12/2022 22:02:53, Ash Rubigo wrote:
Thanks for the suggestion Jeff.
Increased the amount of virtual memory on Windows. Previously it was
allocated by the system, so not sure why it didn't keep increasing as
needed. Anyway, the upper limit is set to 100GB now, so we'll see if
that is sufficient. Currently it's using 40GB after a few hours of
dumping this one revision with no end in sight.
On 27/12/2022 18:13:12, Jeffrey Walton wrote:
On Tue, Dec 27, 2022 at 1:05 PM Ash Rubigo <ashrub...@gmail.com> wrote:
I'm trying to extract projects from a large repository into their own
separate repositories.
I understand to use `svnadmin dump`, then `svndumpfilter`, and finally
`svnadmin load`.
Trouble is during `svnadmin dump` one of the revisions results in an
'out of memory' error. The revision in question is large, on the order
of 20GB and I only have 16GB of RAM.
I have tried incrementally dumping, but had the same issue.
Is it really the case that if a revision is larger than the available
RAM it cannot be dumped?
Just a thought, but it does not answer the question...
Use GParted, and increase the swap file to say, 64 GB. Then set
swappiness to a low value, like 2. The low swappiness value will keep
most stuff in RAM, and spill over to disk rarely. Most of the swap
file will remain unused. But it should allow your dumps to proceed.
Jeff
--
Regards,
Ash Rubigo
