-
Notifications
You must be signed in to change notification settings - Fork 199
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
Debug level #1
Comments
One, somewhat orthogonal thing would be to guard the debug logging statements with a global |
I believe @tk721's idea will lead to a better performance since the "undesired" code will be removed from bytecode due to compiler optimization. Since performance matters, I think it is better choice than the one I myself suggested, so +1 for Teemu's suggestion. |
This would be a nice feature. In addition to what @julianofischer and @tk721 have already mentioned, perhaps we can have different levels of information emission, such as |
+1 for @tk721's idea. There is already support for different debug levels at the core/Debug.java, but apparently I forgot to define the constants for them. Should fix it. |
Suggestion:
When running MaxPropRouter, there is a snippet of code frequently called (from routing.maxprop.MeetingProbability, which prints some information in output stream.
It is frequently annoying and could lead to performance degradation.
Perhaps the best default option for debugging is not debugging, actually.
Actually, in my code I changed the snippet in order to workaround:
It would be nice a (not hardcoded) way to disable it (increase the debug level).
I could contribute with a pull request if the authors agree to reade the debug level from settings:
The text was updated successfully, but these errors were encountered: