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

Diagram FIM pipeline I/O #1266

Open
JamesColl-NOAA opened this issue Aug 26, 2024 · 1 comment
Open

Diagram FIM pipeline I/O #1266

JamesColl-NOAA opened this issue Aug 26, 2024 · 1 comment
Assignees
@JamesColl-NOAA
Labels
documentation Improvements or additions to documentation

Comments

@JamesColl-NOAA
Copy link
Contributor

No description provided.

@JamesColl-NOAA JamesColl-NOAA self-assigned this Aug 26, 2024
@JamesColl-NOAA JamesColl-NOAA added the documentation Improvements or additions to documentation label Aug 26, 2024
@RobHanna-NOAA
Copy link
Contributor

I can likely help with this Jim when you get there. I know it pretty well of course. Pretty shocking actualy. I did a very rough calc on last year and I think it was doing in the range of 40+ TiB of read / writes to finish a BED pipeline. Which is mostly why we brought in the fim_temp system to speed this way up and pay way less. Of course that 40 TiB is never at one time. I have lots of details and info on this topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JamesColl-NOAA JamesColl-NOAA

Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JamesColl-NOAA @RobHanna-NOAA