Enable Memory & CPU Profiling for df_engine#2420
Conversation
Codecov Report❌ Patch coverage is ❌ Your patch status has failed because the patch coverage (0.00%) is below the target coverage (70.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #2420 +/- ##
==========================================
- Coverage 88.10% 88.10% -0.01%
==========================================
Files 633 633
Lines 237176 237191 +15
==========================================
- Hits 208975 208967 -8
- Misses 27677 27700 +23
Partials 524 524
🚀 New features to boost your workflow:
|
…sapatrjv/otel-arrow into dev/sapatr/memprofilingwithdhat
| sysinfo.workspace = true | ||
| dhat = "0.3.3" | ||
| ctrlc = "3" | ||
| once_cell = "1" |
There was a problem hiding this comment.
Could of points here
- These 3 crates should be optional and enabled only when
dhat-heapfeature is enabled. - Since this crate already targets Rust 1.87, could we use std::sync::LazyLock here instead of adding once_cell just for this static?
This reverts commit d23af0e.
|
Does this closes the issue #2304 ? |
I don’t think this closes #2304. That issue is about One-Collect support for profiling other processes, while this PR seems focused on CPU/memory profiling for |
|
The issue this fixes: #2297. I modified the PR description. |
lquerel
left a comment
There was a problem hiding this comment.
I think there's a piece of code that needs to be put back, and a potential follow-up PR to track in a GitHub issue.
…sapatrjv/otel-arrow into dev/sapatr/memprofilingwithdhat
|
|
||
| > [!NOTE] | ||
| > In this command, all default features are disabled. | ||
| > Use specific flags to enable individual features. |
There was a problem hiding this comment.
| > Use specific flags to enable individual features. | |
| Use specific flags to enable individual features. |
There was a problem hiding this comment.
Copilot response on it:
and what's your take?
There was a problem hiding this comment.
In my opinion, both approaches will work in this scenario. It will differ when a sentence needs to appear on a separate line. In this case add a blank line with > and then include the next sentence.
|
I had to approve the workflows. @sapatrjv, please accept the invitation that was sent after open-telemetry/community#3352. |
Head branch was pushed to by a user without write access
Pull request was converted to draft
…sapatrjv/otel-arrow into dev/sapatr/memprofilingwithdhat
|
|
||
| > [!NOTE] | ||
| > `dhat` needs a clean shutdown to generate `dhat-heap.json` file. | ||
| > In `df_engine` this can be done manually with Ctrl+C. |
There was a problem hiding this comment.
does Ctrl+C do a clean shutdown? The engine is not yet configured to react to it...
There was a problem hiding this comment.
It does not handle clean shutdown with Ctrl+C. Here is PR #2325 that you own to handle it.
There was a problem hiding this comment.
Until that PR (or another PR which adds this) is merged, lets not mention that engine can do clean shutdown with Ctrl+C
60ceaa2
…default malloc selection (#2695) # Change Summary Enables clippy in the conditional for Jemalloc in src/main.rs, with @sapatrjv. ## What issue does this PR close? Introduced in #2420. Adds `--all-features --workspace -- -D warnings` to the clippy step in `cargo xtask check`. https://cloud-native.slack.com/archives/C08RRSJR7FD/p1776408892537689 ## How are these changes tested? Ran `cargo xtask clippy` on Ubuntu, not sure this actually works in Windows. ## Are there any user-facing changes? No



Change Summary
PR to enable CPU & Memory profiling for df_engine.
What issue does this PR close?
Fixes #2296
Fixes #2297
Fixes #2298
Fixes #2299
:)
How are these changes tested?
Are there any user-facing changes?
N/A