Skip to content

Optimize iterations#137

Merged
DavidWiseman merged 1 commit into
trimble-oss:mainfrom
DavidWiseman:OptimizeIterations
Dec 2, 2025
Merged

Optimize iterations#137
DavidWiseman merged 1 commit into
trimble-oss:mainfrom
DavidWiseman:OptimizeIterations

Conversation

@DavidWiseman

Copy link
Copy Markdown
Collaborator

Iterations now add work to a queue (channel). If a single database is taking a long time to process, the next loop can now begin with that database skipped as it's already in progress. If a single database needs to catch up, it will no longer impact other databases as long as sufficient threads are available.

@DavidWiseman DavidWiseman requested a review from Copilot December 2, 2025 11:21

This comment was marked as outdated.

This comment was marked as resolved.

This comment was marked as resolved.

@DavidWiseman DavidWiseman force-pushed the OptimizeIterations branch 2 times, most recently from da471ba to 36b331c Compare December 2, 2025 14:19
@DavidWiseman DavidWiseman requested a review from Copilot December 2, 2025 14:19

This comment was marked as resolved.

Iterations now add work to a queue (channel).  If a single database is taking a long time to process, the next loop can now begin with that database skipped as it's already in progress.  If a single database needs to catch up, it will no longer impact other databases as long as sufficient threads are available.
@DavidWiseman DavidWiseman merged commit 3573060 into trimble-oss:main Dec 2, 2025
@DavidWiseman DavidWiseman deleted the OptimizeIterations branch December 2, 2025 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants