feat: Add lazy initialization and feature service caching#5924

franciscojavierarceo

Implement performance optimizations for FeatureStore:

Lazy Initialization: Convert registry, provider, and OpenLineage emitter
to lazy properties. Reduces cold start from 2.4s to 0.5s (5x improvement).
Feature Service Caching: Add caching layer for feature service resolution.
Observed 19.6x speedup on cached calls during validation.

Co-Authored-By: Claude Sonnet 4 noreply@anthropic.com

devin-ai-integration

Devin Review found 2 potential issues.

🔴 1 issue in files not directly in the diff

🔴 repr triggers lazy initialization despite comment saying it shouldn't (sdk/python/feast/feature_store.py:194)

The __repr__ method accesses self.registry (the property) instead of self._registry (the private attribute), which triggers lazy initialization of the registry.

Click to expand

How the bug is triggered

The comment on line 193 says "Show lazy loading status without triggering initialization", but line 194 uses self.registry which is a property that initializes the registry if it's None:

# feature_store.py:192-194
def __repr__(self) -> str:
    # Show lazy loading status without triggering initialization
    registry_status = "not loaded" if self.registry is None else "loaded"

The registry property at feature_store.py:206-217 creates the registry when accessed:

@property
def registry(self) -> BaseRegistry:
    if self._registry is None:
        self._registry = self._create_registry()
        ...
    return self._registry

Actual vs Expected

Actual: Calling repr(feature_store) or print(feature_store) triggers registry initialization, negating lazy loading benefits
Expected: Should use self._registry to check status without triggering initialization

Impact

This defeats the purpose of lazy initialization (described as reducing cold start from 2.4s to 0.5s). Any code that prints or logs the FeatureStore object will trigger full initialization.

Recommendation: Change self.registry to self._registry on line 194

View issues and 5 additional flags in Devin Review.

devin-ai-integration

Devin Review found 1 new potential issue.

🔴 1 issue in files not directly in the diff

🔴 repr triggers lazy initialization despite comment saying it shouldn't (sdk/python/feast/feature_store.py:194)

The __repr__ method accesses self.registry (the property) instead of self._registry (the private attribute), which triggers lazy initialization of the registry.

Click to expand

How the bug is triggered

The comment on line 193 says "Show lazy loading status without triggering initialization", but line 194 uses self.registry which is a property that initializes the registry if it's None:

# feature_store.py:192-194
def __repr__(self) -> str:
    # Show lazy loading status without triggering initialization
    registry_status = "not loaded" if self.registry is None else "loaded"

The registry property at feature_store.py:206-217 creates the registry when accessed:

@property
def registry(self) -> BaseRegistry:
    if self._registry is None:
        self._registry = self._create_registry()
        ...
    return self._registry

Actual vs Expected

Actual: Calling repr(feature_store) or print(feature_store) triggers registry initialization, negating lazy loading benefits
Expected: Should use self._registry to check status without triggering initialization

Impact

This defeats the purpose of lazy initialization (described as reducing cold start from 2.4s to 0.5s). Any code that prints or logs the FeatureStore object will trigger full initialization.

Recommendation: Change self.registry to self._registry on line 194

View issue and 6 additional flags in Devin Review.

devin-ai-integration

Devin Review found 1 new potential issue.

🔴 1 issue in files not directly in the diff

🔴 repr triggers lazy initialization despite comment saying it shouldn't (sdk/python/feast/feature_store.py:194)

The __repr__ method accesses self.registry (the property) instead of self._registry (the private attribute), which triggers lazy initialization of the registry.

Click to expand

How the bug is triggered

The comment on line 193 says "Show lazy loading status without triggering initialization", but line 194 uses self.registry which is a property that initializes the registry if it's None:

# feature_store.py:192-194
def __repr__(self) -> str:
    # Show lazy loading status without triggering initialization
    registry_status = "not loaded" if self.registry is None else "loaded"

The registry property at feature_store.py:206-217 creates the registry when accessed:

@property
def registry(self) -> BaseRegistry:
    if self._registry is None:
        self._registry = self._create_registry()
        ...
    return self._registry

Actual vs Expected

Actual: Calling repr(feature_store) or print(feature_store) triggers registry initialization, negating lazy loading benefits
Expected: Should use self._registry to check status without triggering initialization

Impact

This defeats the purpose of lazy initialization (described as reducing cold start from 2.4s to 0.5s). Any code that prints or logs the FeatureStore object will trigger full initialization.

Recommendation: Change self.registry to self._registry on line 194

View issue and 8 additional flags in Devin Review.

franciscojavierarceo and others added 2 commits January 29, 2026 23:31

fix: Add type annotations and formatting fixes for performance optimi… …

2dcfcc1

…zations

franciscojavierarceo requested a review from a team as a code owner January 30, 2026 05:00

devin-ai-integration Bot reviewed Jan 30, 2026

View reviewed changes

Comment thread sdk/python/feast/utils.py Show resolved Hide resolved

devin-ai-integration Bot reviewed Jan 30, 2026

View reviewed changes

franciscojavierarceo added the ok-to-test label Jan 30, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: Add lazy initialization and feature service caching#5924