fix: Add connection pre-warming for DynamoDB async client - #6711
Conversation
|
@jyejare can you look into fix? |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #6711 +/- ##
==========================================
+ Coverage 46.80% 46.82% +0.01%
==========================================
Files 415 415
Lines 50399 50406 +7
Branches 7214 7215 +1
==========================================
+ Hits 23591 23601 +10
+ Misses 25157 25155 -2
+ Partials 1651 1650 -1
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
@nithin42 you can add this new config in documentation specially at Performance tuning guide - DynamoDB tuning section |
|
@ntkathole Done! Documented the new |
ba7c7bb to
cba5604
Compare
|
@ntkathole @jyejare Hello! I've addressed your feedback by documenting the new |
|
@nithin42 I am not able to rebase, please rebase and possibly squash commits |
Add warmup_connections parameter to DynamoDBOnlineStoreConfig and warm up connections via describe_limits inside initialize() method to solve cold-start latency. Also document warmup_connections in the performance tuning guide and reference docs. Fixes feast-dev#6060 Signed-off-by: Nithin <kumbam.nithingoud@gmail.com>
cba5604 to
5eb6037
Compare
|
@ntkathole Done! Rebased onto the latest master and squashed into a single clean commit. |
What this PR does / why we need it
The DynamoDB online store async client doesn't establish actual TCP/TLS connections during
initialize(), causing the very firstget_online_features()call to pay a cold-start overhead (~20ms).This PR adds a
warmup_connectionsboolean option toDynamoDBOnlineStoreConfigand runsdescribe_limits()inside a safetry...exceptblock inDynamoDBOnlineStore.initialize()to pre-warm the connections.Which issue(s) this PR fixes
Fixes #6060
Checks
git commit -s)