Enhance Finesse Benchmark Tool with Cost Estimation and Data Visualization Features

[ibrahim-kabir]

Summary

The finesse benchmark tool currently provides an accuracy score and request time for each JSON file. However, it lacks the capability to generate cost estimates. This tool is responsible for comparing different search engines to discern the best from the worst, and one decisive factor is inevitably the cost incurred by using a tool. Additionally, the tool saves tests locally, and not all the test data is exported to CSV and MD files, such as the entirety of search engine responses. This can result in loss of results and traceability. Finally, it would be beneficial to add a data visualizer such as a graph. Therefore, we are enhancing this tool with the locust-dashboard, which enables us to implement all the aforementioned features.

Tasks:

• Archiving all runs history of the Finesse Benchmark Tool to Datahub #4
• Integrate cost estimation feature into finesse benchmark tool.
• Create Jupyter Notebooks to save data on md and csv file
• Implement a data visualizer on the locust-dashboard, such as a graph, to enhance data analysis capabilities.

Acceptance Criteria

• The finesse benchmark tool successfully generates cost estimates for each search engine.
• All test data, including search engine responses, are saved on datahub
• The implemented data visualizer effectively presents the benchmark results, enhancing data analysis capabilities.

Diagram

    sequenceDiagram
        User ->> Finesse_Tool: Start test
        Finesse_Tool ->> Finesse_Tool: Cost estimate
        Finesse_Tool ->> Datahub: Save test data
        Datahub ->> Locust_Dashboard: Retrieve data
        Locust_Dashboard -->> User: Visualization displayed
        Datahub ->> Jupyter_Notebook: Retrieve data
        Jupyter_Notebook -->> Finesse_Tool: Generate md or csv file

Loading

[rngadam]

Appreciate the diagram but I do not believe it is correct, especially in how it names the processes involved.

Also the individual tasks listed here are large enough to be separate issues.

Let's discuss once we move to a new repo.