Add performance monitoring (CPU and memory usage) functionality to Monitor

[zhangt2333]

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 using Timer wouldn't face breaking changes).

Below are the changes to the logs:

 os.name: Windows 11
 os.version: 10.0
 os.arch: amd64
+Available CPU cores: 32
+Total memory: 130767MB
 Tai-e Version: 0.5.2-SNAPSHOT
...
 Writing analysis plan to C:\Users\admin\Desktop\projects\Tai-e\output\tai-e-plan.yml
-WorldBuilder starts ...
+[WorldBuilder] starts ...
 The world cache mode is enabled.
 World cache not found in C:\Users\admin\Desktop\projects\Tai-e\cache\world-cache-163254446.bin
 Running the WorldBuilder ...
-[Build IR for all methods] elapsed time: 4.63s
+[Build IR for all methods] elapsed time: 3.53s; CPU usage: start 0.64%, peak 89.53%, end 36.64%; Memory usage: start 269MB, peak 2102MB, end 2195MB
-[Run the WorldBuilder] elapsed time: 8.76s
+[Run the WorldBuilder] elapsed time: 7.65s; CPU usage: start 0.00%, peak 89.53%, end 25.48%; Memory usage: start 87MB, peak 2582MB, end 1497MB
 Saving the world cache to C:\Users\admin\Desktop\projects\Tai-e\cache\world-cache-163254446.bin
-[Save the world cache] elapsed time: 2.05s
+[Save the world cache] elapsed time: 2.03s; CPU usage: start 25.48%, peak 25.48%, end 1.68%; Memory usage: start 1497MB, peak 1817MB, end 1817MB
 5729 classes with 55010 methods in the world
-WorldBuilder finishes, elapsed time: 10.82s
+[WorldBuilder] elapsed time: 9.86s; CPU usage: start 0.00%, peak 89.53%, end 1.68%; Memory usage: start 87MB, peak 2518MB, end 1817MB
-pta starts ...
+[pta] starts ...
 Using reflection log from C:\Users\admin\Desktop\projects\Tai-e\java-benchmarks\dacapo-2006\antlr-refl.log
-[Pointer analysis] elapsed time: 1.25s
+[Pointer analysis] elapsed time: 1.38s; CPU usage: start 1.68%, peak 2.98%, end 2.98%; Memory usage: start 1835MB, peak 2321MB, end 2512MB
...
-pta finishes, elapsed time: 1.67s
+[pta] elapsed time: 1.88s; CPU usage: start 1.68%, peak 2.98%, end 2.07%; Memory usage: start 1817MB, peak 2272MB, end 2704MB
-may-fail-cast starts ...
+[may-fail-cast] starts ...
 #may-fail-cast: found 1050 in 6924 reachable relevant Stmts
 #may-fail-cast: found 279 in 1861 reachable relevant Stmts (app)
-may-fail-cast finishes, elapsed time: 0.02s
+[may-fail-cast] elapsed time: 0.05s; CPU usage: start 2.07%, peak 2.07%, end 2.07%; Memory usage: start 2704MB, peak 2704MB, end 2704MB
-poly-call starts ...
+[poly-call] starts ...
 #poly-call: found 1992 in 32673 reachable relevant Stmts
 #poly-call: found 849 in 16855 reachable relevant Stmts (app)
-poly-call finishes, elapsed time: 0.02s
+[poly-call] elapsed time: 0.08s; CPU usage: start 2.07%, peak 2.07%, end 2.07%; Memory usage: start 2704MB, peak 2704MB, end 2704MB
-Tai-e finishes, elapsed time: 12.61s
+[Tai-e] elapsed time: 12.66s; CPU usage: start 0.00%, peak 89.53%, end 2.07%; Memory usage: start 68MB, peak 2704MB, end 2704MB

---

After the team meeting, I implemented these in Monitor and keep Timer for compatibility.

[codecov]

Codecov Report

❌ Patch coverage is 81.96721% with 22 lines in your changes missing coverage. Please review.
✅ Project coverage is 75.69%. Comparing base (7caca0a) to head (8f5762c).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
src/main/java/pascal/taie/util/Monitor.java	74.39%	18 Missing and 3 partials ⚠️
...java/pascal/taie/analysis/pta/PointerAnalysis.java	66.66%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master     #203      +/-   ##
============================================
- Coverage     75.85%   75.69%   -0.17%     
- Complexity     4659     4670      +11     
============================================
  Files           481      482       +1     
  Lines         16060    16150      +90     
  Branches       2198     2203       +5     
============================================
+ Hits          12182    12224      +42     
- Misses         3014     3059      +45     
- Partials        864      867       +3     

Files with missing lines	Coverage Δ
src/main/java/pascal/taie/Main.java	78.87% <100.00%> (ø)
...ain/java/pascal/taie/analysis/AnalysisManager.java	48.38% <100.00%> (ø)
...pascal/taie/analysis/pta/plugin/AnalysisTimer.java	100.00% <100.00%> (ø)
.../taie/analysis/pta/plugin/taint/TaintAnalysis.java	83.33% <100.00%> (ø)
...cal/taie/analysis/pta/toolkit/mahjong/Mahjong.java	100.00% <100.00%> (ø)
...ascal/taie/analysis/pta/toolkit/zipper/Zipper.java	67.01% <100.00%> (ø)
...pascal/taie/frontend/cache/CachedWorldBuilder.java	81.08% <100.00%> (ø)
...main/java/pascal/taie/frontend/soot/IRBuilder.java	77.77% <100.00%> (ø)
.../main/java/pascal/taie/util/RuntimeInfoLogger.java	60.00% <100.00%> (+6.51%)	⬆️
src/main/java/pascal/taie/util/Timer.java	0.00% <ø> (-64.45%)	⬇️
... and 2 more

... and 3 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.