Add standardised benchmarking capabilities, changes to lean_agent #878
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.
Benchmarking
See
benchmark/types
to understand how to implement aBenchmark
.New benchmarks are added as a new folder to
gpt_engineer/benchmark/benchmarks
and with a new entry togpt_engineer/benchmark/benchmarks/load.py
To make it possible to benchmark an agent, just create a function
default_config_agent
that returns an instantiatedAgent
, and then pass the path to that function to the benchmark CLI tool.How to run e.g. lean_agent on the
gpteng
benchmark:python gpt_engineer/benchmark gpt_engineer/core/default/lean_agent gpteng
Results below:
Note that we add local caching to the LLM. Identical calls will reuse the cache stored in .langchain.db. Please delete this file if you want to check for how temperature affects the results.
Also – this is not meant to be merged to refactor. We should merge to main after refactor is merged!