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

LogFunctionNames performance by #41

Open
JoarGjersund opened this issue Jan 2, 2025 · 1 comment
Open

LogFunctionNames performance by #41

JoarGjersund opened this issue Jan 2, 2025 · 1 comment

Comments

@JoarGjersund
Copy link

JoarGjersund commented Jan 2, 2025

as mentioned in renode/renode#330, we should mention the use of cpu LogTranslationBlockFetch true as an alternative to cpu LogFunctionNames true for improving performance when logging function names.

@pgielda
Copy link
Member

pgielda commented Jan 5, 2025

LogFunctionNames will log when the function actually is executed. LogTranslationBlockFetch will only log when the block is first fetched and translated and will not log subsequently if the block is executed from cache and not retranslated. Very often LogTranslationBlockFetch is the good first approximation but its not a "true" trace.

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

2 participants