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

Slow performance on aarch64? #17313

Closed
jboero opened this issue Jul 13, 2021 · 6 comments
Closed

Slow performance on aarch64? #17313

jboero opened this issue Jul 13, 2021 · 6 comments
Labels
bug triage Issue requires triage

Comments

@jboero
Copy link

jboero commented Jul 13, 2021

Title: Possible performance issues with arm64 build on A72 cores?

Description:

envoy version: 98c1c9e/1.18.3/clean-getenvoy-b76c773-envoy/RELEASE/BoringSSL
I recently migrated a use case I've been testing without issues on x86_64 to a high-end aarch64 box I have (Honeycomb LX2K) which has 16xA72 cores @2.2Ghz, 32GB RAM, and 4x10GbE. I notice a single client connection maxes out a CPU core at 30MB/s where x86_64 is able to saturate a 10Gb network fine. Running parallel clients scales linearly (30MB/s per process, maxed core on each). It could just be the CPUs but they tend to perform much better than this in other operations (this isn't a Raspberry Pi). Anwyay I wanted to put this out there in case others noticed performance issues on arm64 or if anybody has an optimized build for aarch64. I have been unable to get my own build together with bazel.

I realize ARM is a bit experimental right now but curious if anybody else notices unexpected performance issues or finds a way to tune things better. This box usually has no problems pushing ~2GB/s in other apps, so 30MB/s is a bit suspect.

@jboero jboero added bug triage Issue requires triage labels Jul 13, 2021
@moderation
Copy link
Contributor

moderation commented Jul 13, 2021

There was a PR recently to address aarch64 performance however it landed after the 1.18.3 release - #16104. The PR has the issue details but the performance issue is due to unaccelerated cryptographic operations - #16105

It would be very interesting to see if you get improved results using a latest main build

@jboero
Copy link
Author

jboero commented Jul 13, 2021

Ah great thanks I'll try that in the next release.

@moderation
Copy link
Contributor

@jboero you are in luck. 1.19.0 was just released - https://groups.google.com/g/envoy-announce/c/26P9tluO6mQ

@jboero
Copy link
Author

jboero commented Jul 14, 2021

Thanks!

@jboero
Copy link
Author

jboero commented Jul 15, 2021

Boom and like that I can now do 300MB/s - up from 30MB/s. Thank you 1.19.

@jboero jboero closed this as completed Jul 15, 2021
@moderation
Copy link
Contributor

That's awesome. Thanks for reporting the update

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

No branches or pull requests

2 participants