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
weight: 1# Defines page ordering. Must be 1 for first (or only) page.
26
-
tool_install: true # Set to true to be listed in main selection page, else false
24
+
tool_install: false# Set to true to be listed in main selection page, else false
27
25
multi_install: false # Set to true if first page of multi-page article, else false
28
26
multitool_install_part: false # Set to true if a sub-page of a multi-page article, else false
29
27
layout: installtoolsall # DO NOT MODIFY. Always true for tool install articles
28
+
29
+
build:
30
+
list: false
31
+
render: true
30
32
---
31
33
32
34
The Arm System Characterization Tool (ASCT) is a command-line utility for running low-level benchmarks, diagnostic scripts, and system tests to analyze and debug performance on Arm-based platforms. ASCT provides a standardized environment for evaluating key hardware characteristics and is especially suited for platform bring-up, system tuning, and architectural comparison tasks.
@@ -82,10 +84,10 @@ ASCT is distributed as a Python package and requires Python 3.10 or later.
82
84
83
85
Download the latest ASCT release from the [artifacts.tools.arm.com](https://artifacts.tools.arm.com/asct/dist/) page.
This installs ASCT to `/usr/local/bin` making it available system-wide. Installing to `/usr/local/bin` instead of the default `~/.local/bin` allows you to run ASCT with `sudo`, which is required for some benchmarks to access system resources and configure huge pages.
@@ -115,7 +117,7 @@ asct version
115
117
The output is similar to:
116
118
117
119
```output
118
-
ASCT 0.4.1+a304bc8
120
+
ASCT 0.4.2+3b955c2
119
121
```
120
122
121
123
You can also display the help information:
@@ -261,6 +263,14 @@ ASCT provides several additional options:
261
263
-`--no-cache` - Disable cached benchmark data
262
264
-`--clear-cache` - Clear cached benchmark data
263
265
266
+
Setting `--log-level` to `debug` is useful if the tests are not running due to permission settings or a missing software dependency.
267
+
268
+
Some of the tests also generate graphs.
269
+
270
+
An example of a bandwidth graph is shown below:
271
+
272
+

0 commit comments