Skip to content

Conversation

@pantierra
Copy link
Contributor

Closes #201

@pantierra pantierra force-pushed the feature/concurrency-autosclaing branch from d062b41 to 0833cb5 Compare November 18, 2025 10:07
@pantierra pantierra self-assigned this Nov 18, 2025
Comment on lines 390 to 396
# Multidim service (similar to raster - CPU intensive operations)
WEB_CONCURRENCY: "4"
##############
# Database Pool
##############
DB_MIN_CONN_SIZE: "1"
DB_MAX_CONN_SIZE: "3"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Worth just maintaining the same comment structure? We've got it duplicated everywhere else?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe too much. Reduced it.

@pantierra pantierra force-pushed the feature/concurrency-autosclaing branch from 0833cb5 to 386abd2 Compare November 18, 2025 21:35
@pantierra pantierra force-pushed the feature/concurrency-autosclaing branch from 386abd2 to 4f1c2d6 Compare November 18, 2025 23:30
@pantierra
Copy link
Contributor Author

@vincentsarago would you agree with the defaults being set here?

Copy link
Contributor

@ciaransweet ciaransweet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, guess you still want @vincentsarago 's input!

@pantierra
Copy link
Contributor Author

Thanks both for your reviews!

@pantierra pantierra merged commit 1943630 into main Nov 20, 2025
4 checks passed
@pantierra pantierra deleted the feature/concurrency-autosclaing branch November 20, 2025 11:20
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.

Performance settings (concurrency vs. autoscaling)

4 participants