GeezerVison is showing github.com — feat: Optimize container infrastructure for production by franciscojavierarceo · Pull Request #5881 · feast-dev/feast
Conversation
- Add multi-worker configuration with auto-scaling (CPU * 2 + 1)
- Add worker connections, max-requests, and jitter parameters
- Optimize registry TTL from 2s/5s to 60s for reduced refresh overhead
- Support --workers=-1 for automatic worker count calculation
- Add worker recycling to prevent memory leaks
Expected Impact:
- 300-500% throughput increase with proper worker scaling
- Reduced registry refresh overhead
- Better resource utilization in containerized environments
What this PR does / why we need it:
make serving faster
Which issue(s) this PR fixes:
Misc
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
- Add multi-worker configuration with auto-scaling (CPU * 2 + 1)
- Add worker connections, max-requests, and jitter parameters
- Optimize registry TTL from 2s/5s to 60s for reduced refresh overhead
- Support --workers=-1 for automatic worker count calculation
- Add worker recycling to prevent memory leaks
Expected Impact:
- 300-500% throughput increase with proper worker scaling
- Reduced registry refresh overhead
- Better resource utilization in containerized environments
Co-Authored-By: Claude Sonnet 4 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
- Document new worker configuration options (--workers, --worker-connections, etc.)
- Add performance best practices for production deployments
- Include guidance on registry TTL tuning and container deployments
- Provide examples for development vs production configurations
Co-Authored-By: Claude Sonnet 4 <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
YassinNouh21
pushed a commit
to YassinNouh21/feast
that referenced
this pull request
Feb 7, 2026
* feat: optimize container infrastructure for production
- Add multi-worker configuration with auto-scaling (CPU * 2 + 1)
- Add worker connections, max-requests, and jitter parameters
- Optimize registry TTL from 2s/5s to 60s for reduced refresh overhead
- Support --workers=-1 for automatic worker count calculation
- Add worker recycling to prevent memory leaks
Expected Impact:
- 300-500% throughput increase with proper worker scaling
- Reduced registry refresh overhead
- Better resource utilization in containerized environments
Co-Authored-By: Claude Sonnet 4 <[email protected]>
* style: fix ruff formatting in serve.py
Co-Authored-By: Claude Sonnet 4 <[email protected]>
* docs: add performance configuration documentation
- Document new worker configuration options (--workers, --worker-connections, etc.)
- Add performance best practices for production deployments
- Include guidance on registry TTL tuning and container deployments
- Provide examples for development vs production configurations
Co-Authored-By: Claude Sonnet 4 <[email protected]>
* Apply suggestion from @franciscojavierarceo
---------
Co-authored-by: Claude Sonnet 4 <[email protected]>
Signed-off-by: yassinnouh21 <[email protected]>
YassinNouh21
pushed a commit
to YassinNouh21/feast
that referenced
this pull request
Feb 7, 2026
* feat: optimize container infrastructure for production
- Add multi-worker configuration with auto-scaling (CPU * 2 + 1)
- Add worker connections, max-requests, and jitter parameters
- Optimize registry TTL from 2s/5s to 60s for reduced refresh overhead
- Support --workers=-1 for automatic worker count calculation
- Add worker recycling to prevent memory leaks
Expected Impact:
- 300-500% throughput increase with proper worker scaling
- Reduced registry refresh overhead
- Better resource utilization in containerized environments
Co-Authored-By: Claude Sonnet 4 <[email protected]>
* style: fix ruff formatting in serve.py
Co-Authored-By: Claude Sonnet 4 <[email protected]>
* docs: add performance configuration documentation
- Document new worker configuration options (--workers, --worker-connections, etc.)
- Add performance best practices for production deployments
- Include guidance on registry TTL tuning and container deployments
- Provide examples for development vs production configurations
Co-Authored-By: Claude Sonnet 4 <[email protected]>
* Apply suggestion from @franciscojavierarceo
---------
Co-authored-by: Claude Sonnet 4 <[email protected]>
Signed-off-by: yassinnouh21 <[email protected]>
jyejare
pushed a commit
to opendatahub-io/feast
that referenced
this pull request
Mar 9, 2026
* feat: optimize container infrastructure for production
- Add multi-worker configuration with auto-scaling (CPU * 2 + 1)
- Add worker connections, max-requests, and jitter parameters
- Optimize registry TTL from 2s/5s to 60s for reduced refresh overhead
- Support --workers=-1 for automatic worker count calculation
- Add worker recycling to prevent memory leaks
Expected Impact:
- 300-500% throughput increase with proper worker scaling
- Reduced registry refresh overhead
- Better resource utilization in containerized environments
Co-Authored-By: Claude Sonnet 4 <[email protected]>
* style: fix ruff formatting in serve.py
Co-Authored-By: Claude Sonnet 4 <[email protected]>
* docs: add performance configuration documentation
- Document new worker configuration options (--workers, --worker-connections, etc.)
- Add performance best practices for production deployments
- Include guidance on registry TTL tuning and container deployments
- Provide examples for development vs production configurations
Co-Authored-By: Claude Sonnet 4 <[email protected]>
* Apply suggestion from @franciscojavierarceo
---------
Co-authored-by: Claude Sonnet 4 <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
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.
|