pkger is very slow for large repos, even though including just one file

Question

pkger is very slow for large repos, even though including just one file

tian000 opened this issue 4 years ago · comments

Napas (Tian) Udomsak commented 4 years ago

I am working in a large monorepo, and would like to run pkger to package just 1 config file. The go.mod file is at the repo root. It takes around 5 minutes because I think it is scanning all the folders to grab folder metadata. Is there a way to make pkger faster for packaging just 1 file in a very large repo?

hackerman · Answer 1 · Mon Aug 17 2020 19:33:21 GMT+0800 (China Standard Time)

We're experiencing the same issue

Eirik Tenold · Answer 2 · Mon Sep 07 2020 12:39:41 GMT+0800 (China Standard Time)

We are also experiencing this in our monorepo. It is structured as a single go module and contain 204 packages/folders. Seems like each folder takes 0.5s to process which makes this really slow.

Hao Tu · Answer 3 · Fri Sep 18 2020 22:39:53 GMT+0800 (China Standard Time)

Is there any solution to imporove this problem?

Márk Sági-Kazár · Answer 4 · Wed Oct 07 2020 05:26:50 GMT+0800 (China Standard Time)

I opened #128 with this issue in mind. I've looked into it, but pkger depends heavily on go list and modules, which makes it easy to use, but less suitable for large projects I guess.