Skip to content

Conversation

andygrove
Copy link
Member

@andygrove andygrove commented Oct 3, 2025

Which issue does this PR close?

Closes #.

Rationale for this change

Debugging.

[Task 486] MemoryPool[ExternalSorter[6]].try_grow(256232960) returning Ok
[Task 486] MemoryPool[ExternalSorter[6]].try_grow(256375168) returning Ok
[Task 486] MemoryPool[ExternalSorter[6]].try_grow(256899456) returning Ok
[Task 486] MemoryPool[ExternalSorter[6]].try_grow(257296128) returning Ok
[Task 486] MemoryPool[ExternalSorter[6]].try_grow(257820416) returning Err
[Task 486] MemoryPool[ExternalSorterMerge[6]].shrink(10485760)
[Task 486] MemoryPool[ExternalSorter[6]].shrink(150464)
[Task 486] MemoryPool[ExternalSorter[6]].shrink(146688)
[Task 486] MemoryPool[ExternalSorter[6]].shrink(137856)
[Task 486] MemoryPool[ExternalSorter[6]].shrink(141952)
[Task 486] MemoryPool[ExternalSorterMerge[6]].try_grow(0) returning Ok
[Task 486] MemoryPool[ExternalSorterMerge[6]].try_grow(0) returning Ok
[Task 486] MemoryPool[ExternalSorter[6]].shrink(524288)
[Task 486] MemoryPool[ExternalSorterMerge[6]].try_grow(0) returning Ok
[Task 486] MemoryPool[ExternalSorterMerge[6]].try_grow(68928) returning Ok

From this, we can make pretty charts to help with comprehension:

image

What changes are included in this PR?

  • Add new config spark.comet.debug.memory
  • Add new LoggingPool that is enabled when the new config is set

How are these changes tested?

@andygrove andygrove changed the title chore: Add memory pool trace logging [WIP] chore: Add memory pool trace logging [WIP] [skip-ci] Oct 3, 2025
@andygrove andygrove changed the title chore: Add memory pool trace logging [WIP] [skip-ci] chore: Add memory pool trace logging [WIP] [skip ci] Oct 3, 2025
@andygrove andygrove changed the title chore: Add memory pool trace logging [WIP] [skip ci] chore: Add memory pool trace logging [WIP] Oct 3, 2025
@andygrove andygrove marked this pull request as ready for review October 3, 2025 17:36
@andygrove andygrove changed the title chore: Add memory pool trace logging [WIP] chore: Add memory pool trace logging Oct 3, 2025
Comment on lines -170 to -172
debug_native: jboolean,
explain_native: jboolean,
tracing_enabled: jboolean,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rather than adding yet another flag to this API call, I am now using the already available spark config map in native code.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1. The config map should be the preferred method

@codecov-commenter
Copy link

codecov-commenter commented Oct 3, 2025

Codecov Report

❌ Patch coverage is 90.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 59.01%. Comparing base (f09f8af) to head (f6128b5).
⚠️ Report is 573 commits behind head on main.

Files with missing lines Patch % Lines
...ain/scala/org/apache/comet/CometExecIterator.scala 50.00% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #2521      +/-   ##
============================================
+ Coverage     56.12%   59.01%   +2.88%     
- Complexity      976     1457     +481     
============================================
  Files           119      146      +27     
  Lines         11743    13569    +1826     
  Branches       2251     2358     +107     
============================================
+ Hits           6591     8008    +1417     
- Misses         4012     4340     +328     
- Partials       1140     1221      +81     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.


impl MemoryPool for LoggingPool {
fn grow(&self, reservation: &MemoryReservation, additional: usize) {
println!(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be println as info! or trace! ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess info! would be ok. I pushed that change. If we use trace! then we would have to set spark.comet.debug.memory=true and also configure trace logging for this one file, which seem like overkill for a debug feature

Comment on lines -170 to -172
debug_native: jboolean,
explain_native: jboolean,
tracing_enabled: jboolean,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1. The config map should be the preferred method


impl MemoryPool for LoggingPool {
fn grow(&self, reservation: &MemoryReservation, additional: usize) {
info!(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be useful to add a debug! log message which has the backtrace of where this was requested from?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea. I updated try_grow to log the Err if it fails. This should contain the backtrace if the backtrace feature is enabled, but I need to test this out locally.

Copy link
Contributor

@parthchandra parthchandra Oct 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking that we do this for every call (not just for the error) so we can trace the precise origins of the allocations. Probably should be a trace message (not a debug) though. This is merely a suggestion though, I'll leave it to you to decide if it is useful.
Logging the backtrace on error is definitely useful.

@andygrove
Copy link
Member Author

Updated example chart now that this is logging the correct info:

data stacked_cumulative

@andygrove andygrove marked this pull request as draft October 3, 2025 20:53
@andygrove
Copy link
Member Author

moving to draft while I work on the Python scripts

@andygrove
Copy link
Member Author

Still experimenting...

mem_chart

@andygrove
Copy link
Member Author

Chart now shows when try_grow failed:

mem_chart

@andygrove andygrove changed the title chore: Add memory pool trace logging chore: Add memory reservation debug logging and visualization Oct 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants