Add performance monitoring (CPU and memory usage) functionality to Timer #203
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the team meeting about #178, we revisited the user requirements, and we decided to create a lightweight performance monitoring solution focused on internal execution phases.
I directly added memory and CPU usage statistics functionality to the
Timer
utility class that was originally used for timing.Although this extends the functionality beyond what the
Timer
name suggests, since the code modifications are minimal, I'm still hesitating whether we should rename it (if we were to rename it, we might need to keep the Timer class and add a new class to maintain backward compatibility so that other branches usingTimer
wouldn't face breaking changes).Below are the changes to the logs: