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

metrics should have an unsafe option #200

Open
mfbalin opened this issue Jul 27, 2024 · 0 comments
Open

metrics should have an unsafe option #200

mfbalin opened this issue Jul 27, 2024 · 0 comments

Comments

@mfbalin
Copy link

mfbalin commented Jul 27, 2024

🚀 The feature

For high performance low latency use cases, any CPU GPU synchronization kills the performance. The metrics should have an unsafe option assuming all inputs are valid and avoid any synchronization such as here:

if num_label_is_zero.any():
logging.warning(
"Warning: Some classes do not exist in the target. F1 scores for these classes will be cast to zeros."
)

Motivation, pitch

I am developing a high performance GNN library where each iteration can take less than 10ms. Any synchronization kills the performance of my use case.

Alternatives

No response

Additional context

No response

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

1 participant