You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/tidal tools/machine_stats.md
+24Lines changed: 24 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -137,6 +137,18 @@ With this, you can also access this information on the Tidal Accelerator platfor
137
137
138
138
{% include image.html file="process_stats.png" %}
139
139
140
+
#### Capture CPU Utilization Time Series Data
141
+
142
+
To capture point-in-time CPU utilization data, you can use the `-CPUUtilizationOnlyValue` and `-CPUUtilizationTimeout` flags. When run this way, machine stats will capture the current CPU utilization of the machine, rather than peak and average over a given interval.
When run in a scheduled task (as outlined in the following section), it's possible to use machine stats to continuously capture CPU utilization data for a given server over time.
151
+
140
152
#### Run Machine Stats in a Scheduled Task
141
153
142
154
To run Machine Stats in a Windows scheduled task, we must first create the script which the scheduled task will execute. If you want to save the results as json files to the current directory, with a timestamp in the filename, you can use something like this (remember to replace `<path>` with the correct path):
@@ -331,6 +343,18 @@ With this, you can also access this information on the Tidal Accelerator platfor
331
343
332
344
{% include image.html file="process_stats.png" %}
333
345
346
+
#### Capture CPU Utilization Time Series Data
347
+
348
+
To capture point-in-time CPU utilization data, you can use the `--cpu-utilization-only-value` and `--cpu-utilization-timeout` flags. When run this way, machine stats will capture the current CPU utilization of the machine.
When run in a cron job (as outlined in the following section), it's possible to use machine stats to continuously capture CPU utilization data for a given server over time.
357
+
334
358
#### Run Machine Stats on a Cron Job
335
359
336
360
By leveraging cron, you can run Machines Stats on a schedule to gather data over a period of time.
0 commit comments