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

Tpetra: Make CrsGraph MatrixMarket I/O memory scalable #1017

Open
mhoemmen opened this issue Jan 20, 2017 · 6 comments
Open

Tpetra: Make CrsGraph MatrixMarket I/O memory scalable #1017

mhoemmen opened this issue Jan 20, 2017 · 6 comments
Labels
DO_NOT_AUTOCLOSE This issue should be exempt from auto-closing by the GitHub Actions bot. pkg: Tpetra story The issue corresponds to a Kanban Story (vs. Epic or Task)

Comments

@mhoemmen
Copy link
Contributor

mhoemmen commented Jan 20, 2017

@trilinos/tpetra
Epic: #769

MatrixMarket input and output (I/O) for Tpetra::CrsGraph currently gathers the whole matrix to Process 0 before writing it. This is not memory scalable. "Memory scalable" means that no single process has to store more than a small constant factor times the maximum per-process memory usage of the distributed data structure. See also #352 and #353.

@mhoemmen mhoemmen added story The issue corresponds to a Kanban Story (vs. Epic or Task) pkg: Tpetra labels Jan 20, 2017
@kddevin
Copy link
Contributor

kddevin commented Feb 17, 2021

#7045 begins to address this issue

@github-actions
Copy link

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and/or remove the MARKED_FOR_CLOSURE label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE.
If it is ok for this issue to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.

@github-actions github-actions bot added the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 19, 2022
@kddevin kddevin removed the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 21, 2022
@github-actions
Copy link

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and/or remove the MARKED_FOR_CLOSURE label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE.
If it is ok for this issue to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.

@github-actions github-actions bot added the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 22, 2023
@mhoemmen
Copy link
Contributor Author

autobot begone

@github-actions github-actions bot removed the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 25, 2023
Copy link

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and/or remove the MARKED_FOR_CLOSURE label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE.
If it is ok for this issue to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.

@github-actions github-actions bot added the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 28, 2024
@GrahamBenHarper
Copy link
Contributor

this sounds important to not close. begone bot

@GrahamBenHarper GrahamBenHarper added DO_NOT_AUTOCLOSE This issue should be exempt from auto-closing by the GitHub Actions bot. and removed MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. labels Feb 29, 2024
@jhux2 jhux2 added this to Tpetra Aug 12, 2024
@jhux2 jhux2 moved this to Needs Triage in Tpetra Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DO_NOT_AUTOCLOSE This issue should be exempt from auto-closing by the GitHub Actions bot. pkg: Tpetra story The issue corresponds to a Kanban Story (vs. Epic or Task)
Projects
Status: Needs Triage
Development

No branches or pull requests

3 participants