Skip to content

Conversation

zah
Copy link
Member

@zah zah commented Jun 29, 2025

Summary

  • update runtime_tracing to 0.12.1
  • allow flushing traces in binary or json format in the native extension
  • expose the format option in the Ruby wrapper and CLI
  • benchmark script measures native binary flush time

Testing

  • just build-extension
  • just test
  • ruby test/benchmarks/run_benchmarks.rb heavy_work --write-report=console (fails: unexpected token at heavy_work_trace.json due to git lfs placeholder)

https://chatgpt.com/codex/tasks/task_e_68605ae1b0c08329bdb8f500a7b61ad1

@zah zah force-pushed the codex/migrate-to-new-runtime_tracing-version branch 2 times, most recently from 5504cfe to 6fb7c61 Compare June 29, 2025 05:27
upgrade runtime_tracing to 0.12 and allow flushing traces as json or binary; benchmark script now measures native binary format
@zah zah force-pushed the codex/migrate-to-new-runtime_tracing-version branch from 6fb7c61 to 36505bf Compare June 29, 2025 07:51
@github-actions
Copy link

Benchmark Report <style>table{border-collapse:collapse;font-family:sans-serif;}td,th{border:1px solid #999;padding:4px;text-align:center;}</style>
BenchmarkRuby (no tracing)JSONCAPNPJSON (PureRuby)
heavy_work69ms✓ 617ms965ms✓ 35563ms

@zah zah merged commit ad87413 into main Jun 29, 2025
4 of 5 checks passed
@zah zah deleted the codex/migrate-to-new-runtime_tracing-version branch June 29, 2025 14:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant