Log model and usage stats in record.sampling
#1449
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's often useful to know the token expenditure of running an eval, especially as the number of evals in this repo grows. Example feature request, and we also rely on this e.g. here.
Computing this manually is cumbersome, so this PR suggests to simply log the usage receipts (for token usage) of each API call in
record.sampling
. This makes it easy for one to sum up the token cost of an eval given a logfile of the run.Here is an example of a resulting
sampling
log line after this change (we add thedata.model
anddata.usage
fields):