8000 More cpu usage / throttling after switching to from scratch · Issue #13 · coord-e/magicpak · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

More cpu usage / throttling after switching to from scratch #13

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.

Sign up for GitHub

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

Jump to bottom
Open
8000
grosser opened this issue Jun 6, 2022 · 4 comments
Open

More cpu usage / throttling after switching to from scratch #13

grosser opened this issue Jun 6, 2022 · 4 comments
Assignees
@coord-e

Comments

@grosser
Copy link
grosser commented Jun 6, 2022

for a ruby example app that we converted we saw cpu and throttling jump pretty bad (it's not a big deal since it's still super small), but some guidance on why this might happen and how to avoid it would be great for onboarding apps where performance actually matters.

image
@coord-e
Copy link
Owner
coord-e commented Nov 14, 2022

I tried to reproduce this using minimal Sinatra HTTP server but I couldn't find any significant difference.
https://gist.github.com/coord-e/cf89553d0f5f3078720db14432ac857a
cpu usage

@grosser Could you give me some more details about the situation so that I can reproduce this on my end? What kind of application are you running?

@coord-e coord-e self-assigned this Nov 14, 2022
@grosser
Copy link
Author
grosser commented Nov 14, 2022

ruby worker ... I'll try to reproduce and add more details if I can 🤞

@grosser
Copy link
Author
grosser commented Dec 2, 2022 •
edited
Loading
  • ran simple benchmark and no success

git clone https://github.com/Shopify/yjit-bench into lib
then run via ruby -rrbconfig -I lib/yjit-bench/harness lib/yjit-bench/benchmarks/binarytrees/benchmark.rb

  • binarytrees same
  • etanni 10% slower
  • fannkuchredux same
    ... so idk what's going on there

also tried running with gcr.io/distroless/base-debian10 (and without jmalloc) which gave less throttling but same cpu usage
normal (first 1/2), ubuntu (Fri 2), debian (last 1/8th)
SCR-20221202-vev

I'll need to look into our app and see if some specific action is slower than normal

@grosser
Copy link
Author
grosser commented Dec 11, 2022

this is from a stats app that does lots of small things, so tried each individually by making it do 100 iterations in a loop

  • computation heavy (PodHealth): same
  • network heavy (PodNetworkError): same
  • aws api heavy (MissingAmiReporter): same
  • connecting to internal app (VaultReachability): same
    ... so maybe this is just some reporting foobar 🤷

idk where to go from here ... maybe someone who knows more about how container metrics are reported can chime in ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@coord-e coord-e

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@grosser @coord-e
0