-
Notifications
You must be signed in to change notification settings - Fork 23
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
base: develop
Are you sure you want to change the base?
Conversation
LGTM |
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
@@ -70,23 +70,33 @@ | |||
|
|||
#define CHAI_UNUSED_ARG(X) | |||
|
|||
#if !defined(CHAI_DISABLE_ALL_LOGGING) | |||
#if !defined(CHAI_DISABLE_RM) |
There was a problem hiding this comment.
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?
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.