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
I've noticed that evaluate is taking over a minute and a half to run on a single example. I eventually tracked it down to the fact that LangSmith is calling some git commands in the background and this takes about 1m:28s (the actual evals take about 2 seconds).
Suggestion:
Is this really necessary? I should be able to run evals without involving git, no? Even if I'm an outlier with my very slow git repo, it still seems like overhead that could be avoided.
I don't want all that git info as my metadata anyway, I would like a way to opt out (or in).
If you're wondering why my git is so slow, it's because I'm using WSL2 + with files on Windows which is known to be slow with git. It's perfectly fine most of the time, but things like git status take a while. This is the first time I've come across a Python package that called git, so had never really noticed the problem until now.
The text was updated successfully, but these errors were encountered:
Issue you'd like to raise.
I've noticed that
evaluate
is taking over a minute and a half to run on a single example. I eventually tracked it down to the fact that LangSmith is calling some git commands in the background and this takes about 1m:28s (the actual evals take about 2 seconds).Suggestion:
Is this really necessary? I should be able to run evals without involving git, no? Even if I'm an outlier with my very slow git repo, it still seems like overhead that could be avoided.
I don't want all that git info as my metadata anyway, I would like a way to opt out (or in).
If you're wondering why my git is so slow, it's because I'm using WSL2 + with files on Windows which is known to be slow with git. It's perfectly fine most of the time, but things like
git status
take a while. This is the first time I've come across a Python package that called git, so had never really noticed the problem until now.The text was updated successfully, but these errors were encountered: