roachtest: enable cpu profiler on restore tests #108048
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This change is |
`restore/tpce/400GB/aws/nodes=8/cpus=8` recently failed with high CPU usage on one node cockroachdb#106140. The high CPU usage was attributed within replication, however we were unable to determine where exactly. Enable the automatic CPU profiler on `restore/*` roachtests, which will collect profiles once normalized CPU utilization exceeds 70%. Note this is supposed to be a temporary addition, which will be subsumed by cockroachdb#97699. Informs: cockroachdb#106140 Release note: None
kvoli
force-pushed
the
230802.roachtest-enable-cpu-profiler-on-restore
branch
from
6329dba
to
ab83b82
Compare
|
No longer necessary -- #106140 was closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
restore/tpce/400GB/aws/nodes=8/cpus=8recently failed with high CPU usage on one node #106140. The high CPU usage was attributed within replication, however we were unable to determine where exactly.Enable the automatic CPU profiler on
restore/*roachtests, which will collect profiles once normalized CPU utilization exceeds 70%.Note this is supposed to be a temporary addition, which will be subsumed by #97699.
Informs: #106140
Release note: None