Skip to content

docs: Add online server performance tuning guide#6227

Open
ntkathole wants to merge 1 commit intofeast-dev:masterfrom
ntkathole:performance_tuning
Open

docs: Add online server performance tuning guide#6227
ntkathole wants to merge 1 commit intofeast-dev:masterfrom
ntkathole:performance_tuning

Conversation

@ntkathole
Copy link
Copy Markdown
Member

@ntkathole ntkathole commented Apr 5, 2026

Summary

This PR adds a comprehensive how-to guide for tuning the Python online feature server
in production Kubernetes deployments with the Feast Operator.

The guide covers:

  • Worker/connection/timeout tuning — Gunicorn worker sizing, connection limits,
    keep-alive, and max-requests recycling with Operator CR and CLI examples
  • Registry cache tuning — explains the synchronous refresh latency problem and
    the cache_mode: thread fix for background refresh
  • Online store selection — comparison of Redis, DynamoDB, PostgreSQL, Bigtable,
    and Cassandra with latency guidance and store-specific tuning (connection pooling,
    batch parallelism, retry modes, consistent reads)
  • Batch size tuning — per-store batch size comparison and profiling guidance
  • ODFV optimization — native Python mode vs pandas, write-time transforms
  • Horizontal scaling — expected scaling efficiency table and HA summary
    (links to scaling-feast.md for full YAML examples)
  • Metrics setup — Prometheus built-in metrics (key metrics table, alert rule
    examples) and OpenTelemetry Operator integration
  • Network latency optimization — co-location, VPC endpoints / Private Link
    for AWS/GCP/Azure, DNS caching

The guide is registered in docs/SUMMARY.md under How-to Guides, after
"Feast on Kubernetes". It cross-links to existing reference docs (scaling,
feature server, OpenTelemetry, store-specific pages, ODFVs).


Open with Devin

@ntkathole ntkathole self-assigned this Apr 5, 2026
@ntkathole ntkathole requested a review from a team as a code owner April 5, 2026 08:38
@ntkathole ntkathole force-pushed the performance_tuning branch 2 times, most recently from e7fad2d to 44c5256 Compare April 5, 2026 08:51
@ntkathole ntkathole force-pushed the performance_tuning branch 6 times, most recently from 0c360de to a4526c9 Compare April 5, 2026 11:59
@ntkathole ntkathole force-pushed the performance_tuning branch from a4526c9 to b17d2c2 Compare April 5, 2026 12:17
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

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

Devin Review found 1 new potential issue.

View 3 additional findings in Devin Review.

Open in Devin Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant