Performance Issues with Trunk

[vtsachev]

Description:
• Commit actions can take up to two minutes, slowing down development workflows.
• Trunk consumes a significant portion of system RAM (up to 1/4 of 16GB).
• VSCode integration is disrupted, sometimes reporting that Trunk is unavailable for Go file formatting.
• Git branch switching is slow, potentially due to Trunk’s post-checkout hook.
• Machine specs in question: AMD Ryzen™ 7 5800U with 16GB RAM.

User Impact:
• Delays in pushing commits and switching branches reduce overall productivity.
• Resource usage can negatively affect other running applications.
• The VSCode experience degrades with failed Trunk formatting checks.

[andreilgeorgescu]

Agreed. I've always found the trunk extension to be extremely resource intensive and it randomly crashes a lot.