Memory usage during CopyTo

[cbehopkins]

Memory usage during CopyTo

[steveyen]

Thanks for the report and profile! Indeed -- it appears visitNodes() will load all the nodes into memory as it proceeds along. Hmmm. And, I don't have any simple one-liner fix that pops to mind.

Related, gkvlite also hasn't been loaded in my mind for awhile now, as most of my efforts related to a golang storage engine have moved to the github.com/couchbase/moss project as it's better aligned to my current needs.

[cbehopkins]

So I'm currently looking at a multi-line fix myself. Struggling to understand how some of this is supposed to work, but will report back if I make any progress. If you get a Pull request you will know I've had some success. Thanks Chris

…

On 10 May 2017 at 16:30, Steve Yen ***@***.***> wrote: Thanks for the report and profile! Indeed -- it appears visitNodes() will load all the nodes into memory as it proceeds along. Hmmm. And, I don't have any simple one-liner fix that pops to mind. Related, gkvlite also hasn't been loaded in my mind for awhile now, as most of my efforts related to a golang storage engine have moved to the github.com/couchbase/moss project as it's better aligned to my current needs. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ6OU6iUMR8NEKsyWD0KVE_q6LkMSTc4ks5r4dgRgaJpZM4NWhua> .

[cbehopkins]

Forgot to say I fixed this with 7263ff8
I'm working on a bunch of other fixes and in particular trying to make it golint clean. Will produce a pull request when this process is finished