Releases: NSO-developer/nso-memory-utilization-tool
Releases · NSO-developer/nso-memory-utilization-tool
Release list
1.4 Feature Release
1.4
- fix python same timeframe issue
- fix duplicate python package collection
1.3.2 Feature Release
1.3.1
- Add Warning and Critical level logging for physical and allocated memory
- Add Infinity Data Collection and Monitoring feature
- When monitoring, collection time will be infinity
- Fix multiple stability bug and process leaking issue on monitoring feature.
1.3.2
- Add SIGTERM Handling incase "pkill -f" is called
1.3 Feature Release
- Adding Monitor feature for potential proactive actions
- Add physical memory utilization monitoring for overcommit mode 0
- Fix multiple stability issues
1.2.3 Patch Release (Recommended)
- Fix python multiprocessing callpoint-model memory collection issue. Previously these part of memory collection is ignored. Now it counted as the memory utilization for that specific package
- Add Recommendation notice when multiprocessing callpoint-model is detected
- Log clean up.
- CTRL+C SIGINT will now be trapped and handled properly by removing all the cached file and generate diagram with whatever data we have at that moment.
- Fix substring process name ignored issue
- Fine Tune Logging
- Add allocation comparison diagram without CommitAS and CommitLimit for better visualization
1.1 Maintenance Release (Fix multiple stability issues)
- Fix issue during package reload, some data is missing . when new python package join the PythonVM, add 0 data before this package join
- Increase accuracy on capture Time by move Time collection to the main controller plot.sh instead of collect.sh per process
1.0 Initial Release
fix package reload 0 issue