perf(robot-server): Avoid creating process pools that won't do anything #17173
+6
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This optimizes a specific case of robot-server startup.
Details
One of our persistence directory migrations delegates some work to a process pool, for parallelization. But there is a lot of overhead to spawning that process pool (chiefly because of heavy, intertwined imports in the
opentrons
package that we have not yet been able to untangle). The optimization is that if we know we won't have any work to feed that process pool, we can avoid creating it in the first place.The most common practical scenario where this applies is first-time server startup. That happens dozens of times in our integration tests, so this helps developer experience.
Performance testing
On my laptop, this saves ~30 seconds when running
make -C robot-server test
. In CI, it saves about a minute.Correctness testing
We're well-covered by existing integration tests.
Review requests
Does the comment make sense?
Risk assessment
Low.