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

FEAT: Do not put binary functions to the Ray storage multiple times. #6835

Closed
AndreyPavlenko opened this issue Dec 21, 2023 · 0 comments · Fixed by #6836
Closed

FEAT: Do not put binary functions to the Ray storage multiple times. #6835

AndreyPavlenko opened this issue Dec 21, 2023 · 0 comments · Fixed by #6836
Labels
Performance 🚀 Performance related issues and pull requests. Ray ⚡ Issues related to the Ray engine

Comments

@AndreyPavlenko
Copy link
Collaborator

Currently, the binary operations are wrapped into lambdas which are put into the Ray storage on each operation.

@AndreyPavlenko AndreyPavlenko added new feature/request 💬 Requests and pull requests for new features Ray ⚡ Issues related to the Ray engine labels Dec 21, 2023
@YarShev YarShev added Performance 🚀 Performance related issues and pull requests. and removed new feature/request 💬 Requests and pull requests for new features labels Jan 11, 2024
AndreyPavlenko added a commit to AndreyPavlenko/modin that referenced this issue Jan 22, 2024
…ge multiple times.

Added functions cache to RayWrapper.
Removed lambda wrapper for the binary functions.

Signed-off-by: Andrey Pavlenko <andrey.a.pavlenko@gmail.com>
anmyachev pushed a commit that referenced this issue Jan 24, 2024
…imes. (#6836)

Signed-off-by: Andrey Pavlenko <andrey.a.pavlenko@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Performance 🚀 Performance related issues and pull requests. Ray ⚡ Issues related to the Ray engine
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants