8000 Measure peak mem and CPU time · Issue #40 · manticoresoftware/clt · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Measure peak mem and CPU time #40

New issue

Have a question about this project? Sign A1E8 up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Open
donhardman opened this issue Jul 24, 2024 · 0 comments
Open

Measure peak mem and CPU time #40

donhardman opened this issue Jul 24, 2024 · 0 comments
Assignees
@donhardman
Labels
enhancement New feature or request est::size_M

Comments

@donhardman
Copy link
Contributor

It looks like it's possible and might be a good idea to add measurement of 'peak memory' and 'CPU time' usage after each command we run, similar to how we track 'duration'.

To make this happen, we could try tracking the PID of the bash process we run and then use PTY to send commands directly.

It's worth exploring the best approach and testing some ideas to implement this directly within the 'rec' tool's source code.

Once we're done with the measurements, we should think about how we can test it too.
@donhardman donhardman self-assigned this Jul 24, 2024
@donhardman donhardman added the enhancement New feature or request label Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@donhardman donhardman

Labels
enhancement New feature or request est::size_M
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sanikolaev @donhardman
0