Redshift historical retrieval query performance regression
See original GitHub issueThere seems to have been some regression in historical retrieval for Redshift that happened somewhere between 0.14.1 and 0.16.1. A quick summary of one particular user’s issue:
- currently the point-in-time joins on big entity dataframes are slow in Redshift. The entity_df is generated right now by creating e.g. a
user_id
CROSS JOINitem_id
- The tables in question have usually have 2-4 columns per feature view, and models use between 10 - 30 feature views.
@woop had done some quick investigation and the main shift seemed to happen in https://github.com/feast-dev/feast/pull/1911 introduced by @MattDelac
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
Factors affecting query performance - Amazon Redshift
A number of factors can affect query performance. The following aspects of your data, cluster, and database operations all play a part in...
Read more >Improving query performance - Amazon Redshift - 亚马逊云科技
This topic identifies common issues that affect query performance, how to diagnose them, and how to resolve them.
Read more >Amazon Redshift: Ten years of continuous reinvention
Two authors of Amazon Redshift research paper that will be presented at ... with the data lake and query their entire history of...
Read more >Amazon Redshift and the Case for Simpler Data Warehouses
Performance – It is difficult to grow a data warehouse without negatively impacting query performance. Once built,.
Read more >MySQL HeatWave Technical brief - Oracle
Performance Comparison. 25. Classification Results. 25. Regression Results. 26. Integration with Oracle Cloud Services. 26. 1/2 the cost of AWS Redshift and ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Was a slowness (performance regression).
In digging deeper, looks like 0.14.1 was cut Oct 28 and 0.16.1 was cut Dec 11, but this PR was before Oct 28, so shouldn’t have caused the issue.
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.