Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory and recursion issues in tilelive-copy with --parts #170

Open
jflemer-ndp opened this issue Jun 4, 2016 · 1 comment
Open

Memory and recursion issues in tilelive-copy with --parts #170

jflemer-ndp opened this issue Jun 4, 2016 · 1 comment

Comments

@jflemer-ndp
Copy link

Using tilelive-copy with --parts on a large copy seems to have a few issues. In both cases, I was using:
tilelive-copy --concurrency=24 --withoutprogress --timeout=900000 --minzoom=0 --maxzoom=12 --retry=1000 --parts=$PARTS --part=$n mapnik://./project.xml .../foo.mbtiles

Initially, I tried PARTS=1000, and got a Maximum call stack size exceeded. The stack (now gone, sorry) looked to involve a massive recursion on skip()/get(), right about here:

get(push);

I figured even with the recursion, that I'd avoid blowing the stack with PARTS=20, and I did. But each part ended up getting killed or dying due to out of memory. The same command without --parts at all runs just fine (no out of memory errors).

I did not try the pyramid or list scheme, so this may or may not be limited to scanline.

Here are some of the versions in use:

@rclark
Copy link
Contributor

rclark commented Jun 5, 2016

@jflemer-ndp thanks for the report - @jakepruitt also ran into this recently and we'll see if we can pick it apart this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants