Why is the gem bigger than rails ?

[Paul-Yves]

I am currently investigating memory usage on my rails app. I ran a check (bundle exec derailed bundle:mem) to see memory at load time, and discovered that docusign was 46Mb which is a lot (rails is 34Mb and most gems are between 1 and 3 Mb).

Have you investigated why ?

[LarryKlugerDS]

Hmmm good question! I've filed internal ticket DCM-6162 to ask Engineering to investigate.

[MatheusRich]

@Paul-Yves I've investigated a bit in the past and opened this PR fixing it. I think the primary problem is that this gem seems to have its code generated from some tool (probably to generate code across several languages), making the code very unoptimized.

[lordofthedanse]

Can we get an update here, @LarryKlugerDS?

This is bigger than it should be by maybe a factor of 10? AWS S3 gem, for comparison, is ~19MB — that’s the largest gem I’ve ever seen pulled in for a feature.

If there’s a quick fix that lops off 20MB here, that’s a win I would suggest pursuing. Otherwise, this gem (and docusign) are going to be on the chopping block at my company.

@MatheusRich suggested a fix on a branch that was closed with no comments — what’s up there?