Running commands with

PANTS_CONCURRENT=true

has a startup time of about 11 seconds regardless of the command being run. Is this expected behavior or is something off about my system? E.g.

PANTS_CONCURRENT=true pants help

also takes 11 seconds.

I would think so. You're not using the daemon, so it's doing all the heavy dependency tree stuff every time fresh.

Yeah, that's what I was afraid of. I feel like the description in the docs have it switched around?

PANTS_CONCURRENT

default:

False

Enable concurrent runs of Pants. Without this enabled, Pants will start up all concurrent invocations (e.g. in other terminals) without pantsd. Enabling this option requires parallel Pants invocations to block on the first.

To me, this reads as if enabling

PANTS_CONCURRENT

is what will ensure the daemon is used, but it should be the other way around, no?

Yeah, that seems like a typo... Should be "With this enabled"

I'll submit a PR for the docs, @happy-kitchen-89482. But while I'm there:

Enabling this option requires parallel Pants invocations to block on the first.

What does this mean in practice? From my (albeit limited) testing, I'm not seeing an issue where concurrent runs are blocking each other?

If it isn’t set (eg left as the default), running a second pants invocation will block for a little while, printing a message every so often, until the first finishes (or the block times out, if the first one takes too long)

So then this one is swapped around as well, that's what I figured. Alright, thanks!