Very slow west update

I'm having an issue with "west update" taking a very long time on a Windows 11 machine. (Multiple hours) This install of the nRF Connect SDK is just over one month old, and was done on a new Windows 11 install. 

Today, when looking at the notification pop-up on the right side of the status bar (bottom-right of VS Code), I noticed the message "The SDK is out of sync" and a link to "west update". I clicked that update link. What followed was a very slow update process that I terminated after two hours. I have to assume that this isn't intended behaviour, given that simply reinstalling the nRF Connect SDK is far, far faster. 

Looking at the output from "west update", a problem appears to be shown by the repeated messages "Auto packing the repository in background for optimum performance". Each of these messages was followed by a lengthy delay.

The output I saw, up to the point I cancelled the "west update", is in this Onedrive file: 1drv.ms/.../s!ApV4t-ortvt8jaQongwVUHcRApxEow

Is this expected behaviour, or is there something wrong?

Thanks!

Parents
  • Hello,

    Yes, from the logs you shared, I can see frequent messages about auto-packing, which suggests that the auto-packing process is either running more often than necessary or is taking longer than expected. You can manually trigger Git's garbage collection to see if it resolves the issue. This might help consolidate some of the packing processes.

    Refer to the Git documentation on git gc, and you might try running git gc --aggressive --prune=now. From the logs, I don’t see any issues related to the extension.

    Kind regards,

    Abhijith

Reply
  • Hello,

    Yes, from the logs you shared, I can see frequent messages about auto-packing, which suggests that the auto-packing process is either running more often than necessary or is taking longer than expected. You can manually trigger Git's garbage collection to see if it resolves the issue. This might help consolidate some of the packing processes.

    Refer to the Git documentation on git gc, and you might try running git gc --aggressive --prune=now. From the logs, I don’t see any issues related to the extension.

    Kind regards,

    Abhijith

Children
No Data
Related