3.3 KiB
3.3 KiB
2.0.17
- allow to manually clear the event loop when needed it'll clear itself after a given timeout (default to
60000msbut you can specify it with themaxageoption, see this file) 1740a4f - fix elapsed and timestamp calculations on linux #80 e5e2b01
2.0.16
- fix ps on darwin, centisenconds multiplier was wrong and was giving bad cpu usage values bcda538
2.0.15
- Fix Buffer.alloc for node < 4.5
2.0.14
- Version unpublished because of a publish mistake from my part due to a npm error message that confused me. Explanation in isse #71
2.0.12
- fix #69 with
psuse elapsed instead of etime to avoid negative cpu values 0994268 - fix typo in aix
pscommand #68 7d55518
2.0.10
- aix is using ps (was changed by mistake), still no aix CI though
- add alpine to the test suite and make it use procfile
- Improve procfile performances by keeping the procfile open da1c5fb
2.0.8
- After further discussion cpu formula got reverted to the initial one f990f72
2.0.7
2.0.6
- procfiles are back because of performance issues 85e20fa
2.0
- allow multiple pids
- remove
advancedoption - don't use
/proc(procfiles) anymore but usepsinstead - more tests
- API change no more
statmethod, module exports a single function - no more
unmonitormethod, this is handed internally - the default call now returns more data:
{
cpu: 10.0, // percentage (it may happen to be greater than 100%)
memory: 357306368, // bytes
ppid: 312, // PPID
pid: 727, // PID
ctime: 867000, // ms user + system time
elapsed: 6650000, // ms since the start of the process
timestamp: 864000000 // ms since epoch
}
1.2.0
Introduce advanced option to get time, and start
1.1.0
Windows: (wmic) goes back to the first version of wmic, naming wmic process {pid} get workingsetsize,usermodetime,kernelmodetime. CPU usage % is computed on the flight, per pid.
1.0.5
Windows: (wmic) Use raw data instead of formatted this should speed up wmic
0.1.0
API changes:
require('pidusage').stat(pid, fn)
instead of:
require('pidusage')(pid, fn)
Adds a unmonitor method to clear process history