-
Notifications
You must be signed in to change notification settings - Fork 1.2k
docs: Add feature transformation latency blog post #5852
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: franciscojavierarceo <[email protected]>
|
@copilot can you run npm build to make sure the static content renders as expected? |
Build completed successfully! ✅ The blog post renders correctly with the latency comparison image. Here's what was verified: Build output:
The hero image shows the latency decomposition comparison between Pandas and Native Python, and all content sections render properly with code examples and formatting intact. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|

What this PR does / why we need it:
Adds blog post documenting the 10x latency improvements from Native Python Mode transformations and write-time transformations for On Demand Feature Views.
Changes
Blog post: Created
infra/website/docs/blog/feature-transformation-latency.mdcovering:write_to_online_storeparameter for reduced online latencyLatency comparison image: Added
infra/website/public/images/blog/latency.png(174KB) showing Pandas vs Native Python latency decompositionBuild hygiene: Added
infra/website/dist/to.gitignoreto exclude build artifactsBuild Verification
✅ Build completed successfully with
npm run build/blog/feature-transformation-latency/index.html/images/blog/latency.pngWhich issue(s) this PR fixes:
Addresses issue requesting addition of transformation latency blog post to feast.dev.
Misc
Co-authored-by: Francisco Javier Arceo and Shuchu Han (content attribution)
Original prompt
This section details on the original issue you should resolve
<issue_title>Add Feature Transformation Latency Blog Post to Website</issue_title>
<issue_description>Is your feature request related to a problem? Please describe.
Add this blog post to feast.dev site:
Faster On Demand Transformations in Feast 🏎️💨
Thank you to Shuchu Han and Francisco Javier Arceo for their contributions evaluating the latency of transformation for On Demand Feature Views and adding transformations on writes to On Demand Feature Views. Thank you also to Maks Stachowiak, Ross Briden, Ankit Nadig, and the folks at Affirm for inspiring this work and creating an initial proof of concept.
Feature engineering is at the core of building high-performance machine learning models. The Feast team has introduced two major enhancements to On Demand Feature Views (ODFVs), pushing the boundaries of efficiency and flexibility for data scientists and engineers. Here's a closer look at these exciting updates:
1. Turbocharging Transformations with Native Python Mode
Traditionally, transformations in ODFVs were limited to Pandas-based operations. While powerful, Pandas transformations can be computationally expensive for certain use cases. Feast now introduces Native Python Mode, a feature that allows users to write transformations using pure Python.
Key benefits of Native Python Mode include:
![][image1]
Here’s an example of using Native Python Mode for singleton transformations:
This approach aligns with how many data scientists naturally process data, simplifying the implementation of feature engineering workflows.
2. Transformations on Writes: A New Dimension of Latency Optimization
Until now, ODFVs operated solely as transformations on reads, applying logic during online feature retrieval. While this ensured flexibility, it sometimes came at the cost of increased latency during retrieval. Feast now supports transformations on writes, enabling users to apply transformations during data ingestion and store the transformed features in the online store.
Why does this matter?
write_to_online_storeparameter, users can choose whether transformations should occur at write time (to optimize reads) or at read time (to preserve data freshness).Here’s an example of applying transformations during ingestion:
With this new capability, data engineers can optimize online retrieval performance without sacrificing the flexibility of on-demand transformations.
The Future of ODFVs and Feature Transformations
These enhancements bring ODFVs closer to the goal of seamless feature engineering at scale. By combining high-speed Python-based transformations with the ability to optimize retrieval latency, Feast empowers teams to build more efficient, responsive, and production-ready feature pipelines.
For more detailed examples and use cases, check out the documentation for On Demand Feature Views. Whether you’re a data scientist prototyping features or an engineer optimizing a production system, the new ODFV capabilities offer the tools you need to succeed.
The future of Feature Transformations in Feast will be to ...
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.