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

Track Disk I/O Utilization #2404

Open
elgalu opened this issue Jun 14, 2021 · 4 comments
Open

Track Disk I/O Utilization #2404

elgalu opened this issue Jun 14, 2021 · 4 comments

Comments

@elgalu
Copy link

elgalu commented Jun 14, 2021 •
edited

In addition to GPU usage, does modeldb tacks Disk I/O Utilization?
@convoliution
Copy link
Contributor

convoliution commented Jun 14, 2021 •
edited

Hello @elgalu,

It looks like you may have intended to pose this question to the folks at Sacred! Since you've opened an Issue there (IDSIA/sacred#827), would you mind if I closed this one?

@elgalu
Copy link
Author

elgalu commented Jun 14, 2021

Hi! You mean that modeldb internally uses Sacred? I intentionally asked this question in both projects while comparing features between different experiment tracking products.

What about GPU tracking? for instance Wandb tracks, out of the box:
image

@convoliution
Copy link
Contributor

Ah, I understand now. Your question mentioned Sacred specifically, so I hadn't realized you were asking about ModelDB.

Our platform today does not log system performance metrics during training, though capturing richer training metadata is on our roadmap.

@elgalu
Copy link
Author

elgalu commented Jun 14, 2021

Ah, my bad, fixed now:)

@elgalu elgalu mentioned this issue Jun 15, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elgalu @convoliution