[BUG] Windows test is slow compared to tests on other operating systems.

[neoandmatrix]

Describe the bug.

The CI tests that run with every PR on windows operating system are too slow as compared to tests on other operating systems as seen form here https://github.com/asyncapi/cli/actions/runs/13762300626/job/38480929274?pr=1695 .

Expected behavior

Tests should have better performance.

Screenshots

How to Reproduce

1. Make a Pull Request or open any previous one.
2. Check the checks that ran.
3. Observe the test on windows is takes quite a bit longer time than the rest.

🥦 Browser

None

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[neoandmatrix]

actions/runner-images#7320

An issue related to this, looks like it's a widespread issue and common also.

[AayushSaini101]

actions/runner-images#7320

An issue related to this, looks like it's a widespread issue and common also.

• Windows runners are consistently extremely slow compared to Linux and macOS actions/runner-images#7320 (comment)
• Windows runners are consistently extremely slow compared to Linux and macOS actions/runner-images#7320 (comment) Some ideas regarding these, what do you think about the fix for this ? @Shurtu-gal

[Shurtu-gal]

We need a windows environment as we are packaging for it as well. Also we have faced weird edge cases in the past which gets flagged out here, so it is mandatory.

Coming to speed, I was digging through this 2-3 months back, the only thing I could find was windows takes a large amount of time to install the packages itself (maybe due to file system overhead). This is visible in both npm i and generator (as generator also installs npm package).

Would be great if somebody could verify how much a setup and test run takes on a windows environment where packages are not cached v.s cached.

[neoandmatrix]

We need a windows environment as we are packaging for it as well. Also we have faced weird edge cases in the past which gets flagged out here, so it is mandatory.

Coming to speed, I was digging through this 2-3 months back, the only thing I could find was windows takes a large amount of time to install the packages itself (maybe due to file system overhead). This is visible in both npm i and generator (as generator also installs npm package).

Would be great if somebody could verify how much a setup and test run takes on a windows environment where packages are not cached v.s cached.

Thanks for insights, will try to test out if caching can improve this or not.

Thanks.