-
Notifications
You must be signed in to change notification settings - Fork 1k
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
On demand feature views (ODFVs) should use support python dicts #2261
Comments
In your example what types would the |
Numpy arrays should also be a lot better yeah. It might make sense to support both, but really there's also the factor of what the user will have access to at serving time. Seems more likely to be a standard dict. numpy should def be faster, but I also worry since it's significantly more verbose. Could also see a world where we allow both pandas or dicts since pandas will be easier to write the transformations but less performant. In this specific situation, those |
I was actually thinking a dict of 1d Numpy arrays? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
tagging @maksstach who has implemented a version of this on our fork |
I did this one #4045 next I'll do writes. |
I added writes here: #4376 |
In some test benchmarks, using regular python dicts for inputs for executing the transformations is much faster (up to ~10x) than pandas for the online flow. This tends to be the more latency sensitive flow (offline flows seem to be ~40% slower if using vectorized operations).
Something that looks like:
might be similar to what we want
The text was updated successfully, but these errors were encountered: