Difference in the e2e_avg latency observed in the benchmarking tool and Azure portal

We are trying to run our benchmarking exercise using the benchmarking tool for gpt4o, but getting different e2e_avg latency reported on the benchmarking tool and the Azure portal and e2e_avg latency reported on the benchmarking tool is atleast twice of that reported on Azure portal.

**Command used:**
python -m benchmark.bench load --temperature 0.0 --shape-profile custom --deployment 'deployment name' --max-tokens 200 --context-tokens 20000 --api-version 2024-02-01 --rate 10 --duration 600 https://genai-stg-westus3-1.openai.azure.com/

Start with the benchmark.bench load command shown in the issue and reproduce the gpt4o run using the same deployment, API version, rate, duration, and token settings. Compare the tool's e2e_avg with the Azure portal measurement and inspect the benchmark entry points that collect and report latency. Done means identifying and documenting the reason for the discrepancy or defining the required correction; the issue does not name a file or test.

Written by the indexing model from the issue text.