Skip to content

Comments

include input_name in Table.Reader fields#476

Closed
madlep wants to merge 1 commit intobencheeorg:mainfrom
madlep:include-input_name-in-table
Closed

include input_name in Table.Reader fields#476
madlep wants to merge 1 commit intobencheeorg:mainfrom
madlep:include-input_name-in-table

Conversation

@madlep
Copy link
Contributor

@madlep madlep commented Sep 16, 2025

Table.Reader impl doesn't include input_name in the list of output fields.

When a benchmark with multiple inputs is used in a LiveBook and rendered with kino_benchee, all results are combined into a single chart and resulting output is less useful.

livebook-dev/kino_benchee#7 adds faceted charts to display for each input seprately, but needs this data to be exposed by Benchee.

@PragTob
Copy link
Member

PragTob commented Oct 5, 2025

Ah what an oversight!

Thanks a lot for pointing that out! 💚

it looks good overall, but I'm a bit tired right now - I'll wanna review it next week with a bit of a fresher mind but it seems to make sense to me.

I specifically wanna double check job name vs. scenario name usage in there as well and what makes sense (scenario name should be the aggregated name of job and input).

IMG_20211004_091637

@PragTob
Copy link
Member

PragTob commented Oct 21, 2025

Closed in favor of #478 - thank you!

@PragTob PragTob closed this Oct 21, 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.

2 participants