future-coat-901706/26/2023, 6:07 PM
This is using the Kubernetes provider. I've look at the logs with debug logs on, and noticed it's doing some FS scans which takes about a second, I assume building the DAG is also very quick.. I wonder if most of this time is spent making Kubernetes API calls? Are those necessary or is there an option here to introduce a flag to skip all of these? Is there anything else I can do to improve this situation? It would be fantastic if this was under 5 seconds. Thanks!
[2023-06-26T17:24:42.519Z] Resolving 240 modules... [2023-06-26T17:25:14.026Z] Resolving 240 modules... → Done
quaint-dress-83106/27/2023, 11:25 AM
files is broadly more efficient than using
in module configs. For repos with many files, and where possible to use, this is strongly encouraged.
future-coat-901706/27/2023, 3:40 PM
quaint-dress-83106/27/2023, 3:46 PM
future-coat-901706/27/2023, 4:22 PM
quaint-dress-83106/29/2023, 2:16 PM
future-coat-901707/13/2023, 5:44 PM
- unfortunately im seeing almost 2x slower performance
calm-family-2932307/18/2023, 10:08 AM
filters on the modules will increase the speed greatly.
brief-dawn-8895807/18/2023, 2:08 PM
polite-fountain-2801008/14/2023, 1:49 PM
future-coat-901709/08/2023, 6:13 PM
with 0.12.48 vs. 0.13.13 and the results are about a 5 second improvement, from 31s in 0.12 to 25s in 0.13.13. We were hoping to reduce the time to under 10s, wondering if we should see a greater improvement than above? We ran the command with
polite-fountain-2801009/11/2023, 8:52 AM
should be the fastest repo scan mode now for large repos so I'd keep using that. What OS is this on? If you're on MacOS did you make sure you have the ARM build running? Also could you share the debug logs? I would be interesting to see where it's actually spending its time. Previously the graph resolution time was the most expensive part with large projects, so we focused on that first.
future-coat-901709/11/2023, 4:27 PM