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

shush decryption takes a long time on amazonlinux:latest #25

Open
jitran opened this issue Jun 9, 2020 · 2 comments
Open

shush decryption takes a long time on amazonlinux:latest #25

jitran opened this issue Jun 9, 2020 · 2 comments

Comments

@jitran
Copy link

jitran commented Jun 9, 2020

Hello,

I'm using shush_linux_amd64 version 1.4.X on the latest amazonlinux:latest docker image and have noticed that decryption takes roughly 20 seconds on a container with 2cpu 4GB memory. Version 1.3.4 returns a result instantly.

Test steps:

  • shush encrypt KEY-ID "Test" > encrypted
  • shush decrypt < encrypted

Timings:

v1.3.4

real	0m0.063s
user	0m0.031s
sys	0m0.004s

v1.4.0

real	0m20.400s
user	0m0.046s
sys	0m0.000s

v1.4.1

real	0m20.394s
user	0m0.037s
sys	0m0.008s

What are shush's core dependencies? Perhaps I need to update those in my docker image.

Thank you

@ghost
Copy link

ghost commented Jun 9, 2020

@jitran sorry to hear shush is slow for you!

What are shush's core dependencies?

shush does not dynamically load libraries. shush's dependencies are linked into a single static binary at build time. It's very unlikely that updating your docker image will help.

In v1.4.0, there was an update to the AWS SDK.

Based on my recent experience with a similar problem, I believe you are experiencing this issue aws/aws-sdk-go#2972 .

A workaround for this issue is documented in this comment.

Please verify by applying the workaround and repeating your test with the latest version of shush in the docker container.

@jitran
Copy link
Author

jitran commented Jun 15, 2020

Hi David,

Thanks for the details. The suggested workaround resolves the issue for shush version 1.4.0+.

I guess we'll have to wait for a proper AWS SDK fix as setting the max hops for every instance is not ideal.

Cheers

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