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

qs #2

Open
cv-cat opened this issue Nov 24, 2023 · 1 comment
Open

qs #2

cv-cat opened this issue Nov 24, 2023 · 1 comment

Comments

@cv-cat
Copy link

cv-cat commented Nov 24, 2023

By what means can we know the actual memory overhead and runtime while the emulator is running? Where does the source code provide a measure of these two functions?

@shwestrick
Copy link
Contributor

For timings:

For memory, we typically use the "resident set size" as reported by Linux, e.g., /usr/bin/env time -v COMMAND which will report the maximum resident set size of COMMAND. This gives you the peak memory usage of the entire program.

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