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

High I/O Activity when loss_fn is fast #104

Open
fluegelk opened this issue Jan 16, 2024 · 0 comments
Open

High I/O Activity when loss_fn is fast #104

fluegelk opened this issue Jan 16, 2024 · 0 comments
Milestone

Comments

@fluegelk
Copy link

When optimizing a loss_fn with a short runtime, propulate can cause high I/O activity, presumable due to the frequent checkpointing.
Maybe checkpointing only every n-th generation or at most every x seconds could reduce this load.

@mcw92 mcw92 added this to the Checkpointing milestone Aug 15, 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