---
title: "Comment by netproxy on \"Why describe.concurrent Made My Vitest Suite Slower\" | Hashnode"
description: "The file-level scheduling point is the part that clarifies the most. Knowing that concurrent only interleaves tests on the worker a file already has makes the s"
url: "https://hashnode.com/posts/why-describe-concurrent-made-my-vitest-suite-slower/6af753f356fad44e911149a2/comment/6af8ef4ea088ef5f023f53bc"
---

[Discussion](https://hashnode.com/posts/why-describe-concurrent-made-my-vitest-suite-slower/6af753f356fad44e911149a2)

Comment [Why describe.concurrent Made My Vitest Suite Slower](https://hashnode.com/posts/why-describe-concurrent-made-my-vitest-suite-slower/6af753f356fad44e911149a2)

[netproxy](https://hashnode.com/@argumentmoney8117)

[4d ago](https://hashnode.com/posts/why-describe-concurrent-made-my-vitest-suite-slower/6af753f356fad44e911149a2/comment/6af8ef4ea088ef5f023f53bc)

The file-level scheduling point is the part that clarifies the most. Knowing that concurrent only interleaves tests on the worker a file already has makes the slower suite much easier to explain, and the shared handles detail shows why the same change can pass alone and fail in the suite. Thanks for working through the tradeoff so carefully.
