Benchmarks page

[TuanaCelik]

On (old) Haystack website we have a Benchmarks page: https://haystack.deepset.ai/benchmarks/latest
You can select between versions of Haystack and look at their benchmarks but it wasn't regularly updated.

@carlosgauci we now have updated benchmarks that are all here: https://github.com/deepset-ai/haystack/tree/main/docs/_src/benchmarks

Do you think it would be possible as a first iteration:

1. Pull over these benchmarks to haystack-home and create pretty much the same as the previous benchmarks page for 'latest'

As a later iteration (later) we would:

1. Add versions back
2. Automate it so that we push new benchmarks from haystack to haystack-home

To give you an idea of how this benchmarks page was created in the previous website here it is: https://github.com/deepset-ai/haystack-website/blob/source/pages/benchmarks/%5B...slug%5D.tsx

[carlosgauci]

@TuanaCelik I did a quick test here so its definitely possible to use the same type of charts/data, I can work on it after I finish the community changes :)

[TuanaCelik]

Thank you @carlosgauci - I merged the benchmarks page you created :) - let's leave this issue open until we have the previous versions of benchmarks added too

[TuanaCelik]

@carlosgauci I've determined which pervious versions we should add benchmarks for and here they are. Could we do this so that the latest benchmark is always accessible via both a version tag and simply through https://haystack.deepset.ai/benchmarks

You can see how it was done in the previous website here: https://haystack-website-seven.vercel.app/benchmarks/latest

So I'm imagining another version dropdown somewhere on the top of the page. If it makes sense to include a 'latest' tag too, we can also just keep that. 'latest' can just be https://haystack.deepset.ai/benchmarks and a version could be https://haystack.deepset.ai/benchmarks/v1.9.0 and so on :)

So the versions with benchmarks are (with links to the same json files I sent before). The current benchmarks are from v1.9.0
v0.10.0
v0.9.0
v0.8.0
v0.7.0
v0.6.0
v0.5.0

For all of them, the files to look at are the same for all:

reader_performance.json
retriever_map.json
retriever_performance.json
retriever_speed.json

cc: @masci

[carlosgauci]

@TuanaCelik I've added the versions in the linked PR. I left the latest benchmarks on /benchmarks but I can put it on /benchmarks/latest if you prefer that. Let me know if I didn't understand correctly :)