Skip to content
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

Investigate Switching TestOptimizer to use Cascades (and whether or not we want to) #152

Closed
jurplel opened this issue Apr 9, 2024 · 2 comments

Comments

@jurplel
Copy link
Member

jurplel commented Apr 9, 2024

Currently it uses the heuristic optimizer. It seems that to use the cascades optimizer, we might need to introduce a more advanced dummy cost model. It might also be the case that we want to just keep testing on the heuristic optimizer.

See #140 for context.

@AveryQi115
Copy link
Contributor

I think we can use two phase now, no need for using heuristic rules to test cascades. Some rules are not well designed for cascades and jignesh agrees on that too.

@jurplel
Copy link
Member Author

jurplel commented Apr 9, 2024

Ok, I'll just close this issue for now then. Thanks for your feedback!

@jurplel jurplel closed this as completed Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants