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

Size too large for deployment. Possibilities to reduce size? #71

Open
bradyhigginbotham opened this issue Sep 24, 2019 · 1 comment
Open

Comments

@bradyhigginbotham
Copy link

bradyhigginbotham commented Sep 24, 2019

Hey, guys. Thanks for making a great library. I'm getting beautifully optimized routes!

My issue revolves around the resulting library size. Pulling from npm, this library comes in at a chunk of 475 MB, and it looks like the biggest piece is libtools.a @ 317 MB.

Is there any way I can reduce this size? We were really hoping to use this in a Lambda function to build optimal routes for our fleet, but the Lambda max is 250 MB. Is there another version of libtools.a or node-or-tools in general that's a bit slimmer?

Thanks a lot for any help!

Edit: Using --build-from-source doesn't work either if it helps.

@bradyhigginbotham
Copy link
Author

bradyhigginbotham commented Sep 25, 2019

Update to this:

I ended up removing the mason_packages folder in post install. It greatly reduced the size down to about 25 MB and still seems to function just fine. I'm sure I'm missing a binary or something somewhere that's available at the lower size, but this is currently working.

Edit: I'm not closing mainly because my solution is a workaround, and I believe a better one is possible. 😄

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

1 participant