Clear torch.compile cache before each benchmark

[huydhn]

This is a work around that I'm using to run v1 benchmark due to #13392

cc @youkaichao @ywang96

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[ywang96]

Hey @huydhn - Thanks for the PR! I don't think this PR is needed now since we're going to merge #13445. Can you run the benchmark again and see if you're still seeing the same issue?

[huydhn]

Hey @huydhn - Thanks for the PR! I don't think this PR is needed now since we're going to merge #13445. Can you run the benchmark again and see if you're still seeing the same issue?

Sounds good, let me try #13445.

This change might make sense if we want all benchmark runs to be the same (with cold start), but I guess this is a small point.

[youkaichao]

This change might make sense if we want all benchmark runs to be the same (with cold start), but I guess this is a small point.

vLLM guarantees that all compilation finishes in its own warmup phase. no compilation will happen when we serve requests.