Bitbucket custom runner npm step lasts very long time

[Filip Baszak]

I've configured bitbucket custom runner for repository pipelines and everything works fine, instead of first task of pipelines: npm install . 

Complete caches are fetched correctly and I have no idea why it takes so long (4x longer than on bitbucket default pipelines), but any task which comes after first step has very good performance (better than in default bitbucket).

I have set up custom runner using docker in linux docs:
https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-use-runners-for-linux/

Runner is running on my local computer.

Container in which runner runs use only up to 2GB of memory, whats a bit strange, beacuse in bitbucket-pipelines.yaml, I have configuration which increase size (size: x2).

Does anybody had similar issue? What could be causing this problem? Docker container settings or maybe network conneting on my local system?

[Filip Baszak · Accepted solution]

Okay, so I did a bit of testing and figured out that npm commands are so slow due to network speed on WSL.

If anyone will have same problem, I leave very helpful link:

https://github.com/microsoft/WSL/issues/4901

[Syahrul]

G'day, @Filip Baszak 

It's challenging to determine what's happening without reviewing your pipeline build and the runner logs. I see that you have a workspace on a paid plan. Could you please raise a support ticket with us at our Support portal?

We would love to review this behavior and investigate it further.

Regards,
Syahrul

[Filip Baszak]

Thanks for answer @Syahrul , in fact it's not an issue, I was wondering if anybody had similar problem