-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[AMLII-1988] Integrations collected from scheduler (#28517) #28719
Conversation
Co-authored-by: carlosroman <carlos.roman@datadoghq.com> Co-authored-by: gh123man <brian.floersch@datadoghq.com> (cherry picked from commit e1b7c59)
/merge |
🚂 MergeQueue: pull request added to the queue The median merge time in Use |
/merge |
Go Package Import DifferencesBaseline: 150c5c7
|
Serverless Benchmark Results
tl;drUse these benchmarks as an insight tool during development.
What is this benchmarking?The The benchmark is run using a large variety of lambda request payloads. In the charts below, there is one row for each event payload type. How do I interpret these charts?The charts below comes from The benchstat docs explain how to interpret these charts.
I need more helpFirst off, do not worry if the benchmarks are failing. They are not tests. The intention is for them to be a tool for you to use during development. If you would like a hand interpreting the results come chat with us in Benchmark stats
|
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv create-vm --pipeline-id=42724847 --os-family=ubuntu Note: This applies to commit 6ce3266 |
Co-authored-by: carlosroman carlos.roman@datadoghq.com
Co-authored-by: gh123man brian.floersch@datadoghq.com
(cherry picked from commit e1b7c59)
What does this PR do?
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes