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.

Sign up for GitHub

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

Jump to bottom

[Sparse] Avoid conversion overhead between Pytorch sparse tensor and SparseMatrix. #5145

Closed
czkkkkkk opened this issue Jan 11, 2023 · 2 comments
Closed

[Sparse] Avoid conversion overhead between Pytorch sparse tensor and SparseMatrix. #5145

czkkkkkk opened this issue Jan 11, 2023 · 2 comments
Labels
stale-issue topic: Sparse API Work items to implement the new sparse matrix APIs

Comments

@czkkkkkk
Copy link
Collaborator

czkkkkkk commented Jan 11, 2023 •
edited
Loading

🚀 Feature

When converting a SparseMatrix to a Pytorch sparse tensor, the row and column tensors of the SparseMatrix are stacked, which incurs extra time cost and memory consumption. We need a new storage design to avoid such overhead.

Motivation

Alternatives

Pitch

Additional context
@czkkkkkk czkkkkkk added the topic: Sparse API Work items to implement the new sparse matrix APIs label Jan 11, 2023
@github-actions
Copy link

This issue has been automatically marked as stale due to lack of activity. It will be closed if no further activity occurs. Thank you

@czkkkkkk czkkkkkk mentioned this issue Feb 27, 2023
Merged
8 tasks
@czkkkkkk
Copy link
Collaborator Author

czkkkkkk commented Mar 2, 2023

Closed by #5388.

@czkkkkkk czkkkkkk closed this as completed Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale-issue topic: Sparse API Work items to implement the new sparse matrix APIs
Projects
DGL Project Tracker
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@czkkkkkk