You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my current workflow I will create new git worktrees and often several at a time for a new scope of work for AI agents.
At the moment, the performance here leaves my machine basically unusable for the variation of time that it takes to track these new directories. The resource competition is for disk IO and write specifically.
Has anyone come up with any good workarounds for this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
In my current workflow I will create new git worktrees and often several at a time for a new scope of work for AI agents.
At the moment, the performance here leaves my machine basically unusable for the variation of time that it takes to track these new directories. The resource competition is for disk IO and write specifically.
Has anyone come up with any good workarounds for this?
All reactions