Skip to content

feat: add memory profiling support#103

Open
not-matthias wants to merge 3 commits intomasterfrom
cod-2105-support-memory-profiling-for-python
Open

feat: add memory profiling support#103
not-matthias wants to merge 3 commits intomasterfrom
cod-2105-support-memory-profiling-for-python

Conversation

@not-matthias
Copy link
Member

@not-matthias not-matthias commented Jan 28, 2026

No description provided.

@not-matthias not-matthias force-pushed the cod-2105-support-memory-profiling-for-python branch from 55eeef1 to 4bd794f Compare January 28, 2026 17:51
@not-matthias not-matthias marked this pull request as ready for review January 28, 2026 17:51
@not-matthias not-matthias force-pushed the cod-2105-support-memory-profiling-for-python branch from 2351156 to c6a08d7 Compare January 28, 2026 17:59
@avalanche-staging
Copy link

avalanche-staging bot commented Jan 28, 2026

Congrats! CodSpeed is installed 🎉

🆕 330 new benchmarks were detected.

You will start to see performance impacts in the reports once the benchmarks are run from your default branch.

Detected benchmarks


ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.


Open in CodSpeed

Copy link
Contributor

@GuillaumeLagrange GuillaumeLagrange left a comment

Choose a reason for hiding this comment

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

Sorry I meant to request changes

Especially we need to validate the extra stack frame thing in instrumentation by comparing the output to a real prod run!

@not-matthias not-matthias force-pushed the cod-2105-support-memory-profiling-for-python branch from 1f5d7cf to e15aad8 Compare January 30, 2026 14:25
@codspeed-hq
Copy link

codspeed-hq bot commented Jan 30, 2026

Merging this PR will not alter performance

✅ 57 untouched benchmarks
🆕 110 new benchmarks
⏩ 110 skipped benchmarks1

Performance Changes

Mode Benchmark BASE HEAD Efficiency
🆕 Memory test_depth_first_search[4] N/A 0 B N/A
🆕 Memory test_make_peak N/A 0 B N/A
🆕 Memory test_array_alloc[10000] N/A 78.1 KB N/A
🆕 Memory test_sudoku[initial_grid0] N/A 0 B N/A
🆕 Memory test_match_word_pattern[aba-GraphTreesGraph] N/A 0 B N/A
🆕 Memory test_fs_write[10000] N/A 9.8 KB N/A
🆕 Memory test_iir_filter_process N/A 0 B N/A
🆕 Memory test_multiprocessing_map[10000] N/A 4.8 MB N/A
🆕 Memory test_pipe_communication[10000] N/A 24.1 KB N/A
🆕 Memory test_process_creation[cat /dev/null] N/A 287.1 KB N/A
🆕 Memory test_threadpool_map[10] N/A 12.3 KB N/A
🆕 Memory test_threadpool_map[100000] N/A 51.1 MB N/A
🆕 Memory test_hamilton_cycle[graph0] N/A 0 B N/A
🆕 Memory test_generate_parenthesis[3] N/A 0 B N/A
🆕 Memory test_generate_all_combinations[5-4] N/A 0 B N/A
🆕 Memory test_noop_lambda N/A 0 B N/A
🆕 Memory test_hostname_resolution[google.com] N/A 4.5 KB N/A
🆕 Memory test_sum_of_squares[sum_of_squares_sum_comprehension_product] N/A 0 B N/A
🆕 Memory test_sum_squares_slow N/A 135 B N/A
🆕 Memory test_recursive_cached_fibo_10 N/A 568 B N/A
... ... ... ... ... ...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.


Comparing cod-2105-support-memory-profiling-for-python (baf8c5c) with master (adee8a1)

Open in CodSpeed

Footnotes

  1. 110 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@not-matthias not-matthias force-pushed the cod-2105-support-memory-profiling-for-python branch 2 times, most recently from 504d9a3 to 373acb4 Compare January 30, 2026 14:46
@not-matthias not-matthias force-pushed the cod-2105-support-memory-profiling-for-python branch 2 times, most recently from fc8f559 to 597bb2d Compare February 2, 2026 17:44
Copy link
Contributor

@GuillaumeLagrange GuillaumeLagrange left a comment

Choose a reason for hiding this comment

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

lgtm

@not-matthias not-matthias force-pushed the cod-2105-support-memory-profiling-for-python branch from 44487d4 to baf8c5c Compare February 5, 2026 18:22
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.

2 participants