这是indexloc提供的服务,不要输入任何密码
Skip to content
Discussion options

You must be logged in to vote

--dry is really the only option at the moment.

turbo can almost instantly tell if build is cached or if it needs to be re-executed.

this isn't quite true. In order to find an existing cache, turbo has to calculate the hash of the current state of the inputs. If that's slow, then turbo can't know how to check whether cached outputs exist for that hash or not.

However it is incredibly slow (11 seconds in this particular repo):

Could run the command you posted above and add the --cpuprofile=my-profile flag to see where it's spending so much time?

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by mehulkar
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
None yet
2 participants