Skip to content

CHAI_LOG only active with CHAI_DEBUG regardless of RM being enabled #167

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

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

robinson96
Copy link
Contributor

Not sure if this was intentional or not, but CHAI_LOG has been incurring overhead for non debug builds. This has shown up in some of CARE's stress testing kernel launch overhead (can double the cost of a kernel capture and launch). This PR changes CHAI_LOG to only do something when CHAI_DEBUG is defined.

@davidbeckingsale
Copy link
Member

LGTM

@davidbeckingsale
Copy link
Member

I would rather this be a runtime option, because otherwise people will compile with it turned off and it makes it difficult to help debug issues.

Can we maybe remove the messages you were seeing cause a lot of overhead?

…configuration options for disable WARN logging and all logging, refactor logging of movements to only occur when a move occurs
@davidbeckingsale
Copy link
Member

@adayton1 I think your PR #195 is similar to this, and I prefer the fine-grained approach here.

@@ -70,23 +70,33 @@

#define CHAI_UNUSED_ARG(X)

#if !defined(CHAI_DISABLE_ALL_LOGGING)
#if !defined(CHAI_DISABLE_RM)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this still be disabled if the resource manager is disabled? Umpire is required either way, right?

@liu15
Copy link
Collaborator

liu15 commented Apr 11, 2025

@adayton1 I think your PR #195 is similar to this, and I prefer the fine-grained approach here.

I'd also like to see this one merged in, as I have a branch that also duplicates this functionality.

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

Successfully merging this pull request may close these issues.

3 participants