Why library size so large

[feiyuvl]

I found the libmxnet.so is still very large (about 80MB) after I modified the Makefile options. Then I checked the object files in build dir and got this.

The operator dir occupies the most part of the total build size. And some *_gpu.o generated by nvcc is much larger

[chinakook]

Because you build all nvidia sm types such as sm_52

[feiyuvl]

@chinakook No, I modify the make.config, only keep sm_61. Original libmxnet.so is about 500M. What's your library size?

[chinakook]

151MB

[feiyuvl]

@piiswrong Any advices on reducing the gpu obj size?

[szha]

Dynamic links for dependencies such as cudnn tend to reduce the size. What's the problem with the library size? Is there a specific use case that requires small library size for you?

[feiyuvl]

We are deploying mxnet for inference, and need library size as small as possible.

[szha]

Is it on special hardware where disk is very limited?

[feiyuvl]

No, just feel it is too large. A single obj file generated by some op is about 10M which is unreasonable. Maybe the using of template in mshadow causes this.

[szha]

Unrolled loops with instantiation of many types tend to do that... Closing for now since there doesn't seem to be actionable item here. Feel free to reopen if this causes issue.

[tada123]

I get 240MiB libmxnet.so size (built with CUDA disabled), which is really big. Is there any CMake definition/option to reduce it at least under 100MiB (got 217MiB after stripping debugging symbols, which is still very large)?

Could you please reopen the issue?