Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Two questions from the same afternoon of tuning.
Our agents have two cores. I have seen -w 8 in examples, which on our box makes the UI run slower and adds timeouts. What is the actual guidance?
And when a regression run is going to fail, I would rather know in three minutes than in twenty. Is there a fail-fast?
Rules of thumb, in the order I would apply them:
summary.json has durations, and two runs at different -w settle the argument.Fail-fast is --max-failures:
sdods run -p demo-shop -e staging -t @regression --max-failures 1One caveat that has confused people here: on a sharded run it stops that shard. The other shards carry on, because they are separate processes.
From the platform side: on a build agent the core count you read is often the host's, not your quota. If the runner thinks it has 16 cores and the cgroup gives you two, the default worker count is already wrong before you touch a flag.
Pin workers in the process YAML per environment instead of in the workflow file. Then the agent's opinion of itself stops mattering, and the number is somewhere a person will find it.
Have a different question? Ask it.