1phoronix-test-suite(1) General Commands Manual phoronix-test-suite(1)
2
6 phoronix-test-suite - The Phoronix Test Suite is an extensible open-
7 source platform for performing testing and performance evaluation.
8
10 phoronix-test-suite [options]
11 phoronix-test-suite benchmark [test | suite]
12
14 The **Phoronix Test Suite** is the most comprehensive testing and
15 benchmarking platform available for Linux, Solaris, macOS, Windows, and
16 BSD operating systems. The Phoronix Test Suite allows for carrying out
17 tests in a fully automated manner from test installation to execution
18 and reporting. All tests are meant to be easily reproducible, easy-to-
19 use, and support fully automated execution. The Phoronix Test Suite is
20 open-source under the GNU GPLv3 license and is developed by Phoronix
21 Media in cooperation with partners.
22
24 SYSTEM
25 diagnostics This option will print information that is useful to
26 developers when debugging problems with the Phoronix Test Suite
27 and/or test profiles and test suites.
28 interactive
30 A simple text-driven interactive interface to the Phoronix Test
31 Suite.
32 php-conf
34 This option will print information that is useful to developers
35 when debugging problems with the Phoronix Test Suite and/or test
36 profiles and test suites.
37 shell A simple text-driven shell interface / helper to the Phoronix
39 Test Suite. Ideal for those that may be new to the Phoronix Test
40 Suite
41 system-info
43 Display the installed system hardware and software information
44 as detected by the Phoronix Test Suite Phodevi Library.
45 system-sensors
47 Display the installed system hardware and software sensors in
48 real-time as detected by the Phoronix Test Suite Phodevi
49 Library.
50 TEST INSTALLATION
53 force-install [Test | Suite | OpenBenchmarking ID | Test Result]
54 ... This option will force the installation (or re-installa‐
55 tion) of a test or suite. The arguments and process is similar
56 to the install option but even if the test is installed, the
57 entire installation process will automatically be executed. This
58 option is generally used when debugging a test installation
59 problem or wishing to re-install test(s) due to compiler or
60 other environmental changes.
61 install [Test | Suite | OpenBenchmarking ID | Test Result] ...
63 This option will install the selected test(s) inside the testing
64 environment directory. The install process from downloading of
65 the test files to the installation is fully automated. The
66 install option needs to be supplied with the test name or suite
67 as an argument. Optionally, a OpenBenchmarking.org ID or the
68 name of a saved results file can be supplied as well and the
69 test(s) to install will automatically be extracted from that
70 information. If the test is already installed and was run by the
71 latest version of the installation process, no action will be
72 taken. Multiple arguments can be supplied to install additional
73 tests at the same time.
74 install-dependencies [Test | Suite | OpenBenchmarking ID | Test Result]
76 ...
77 This option will install the external dependencies needed by the
78 selected test(s) using the distribution's package management
79 system. For example, some tests depend upon GCC for compiling
80 code. If GCC is not detected on the system, the Phoronix Test
81 Suite will attempt to install GCC using the distribution's pack‐
82 age management system. If you are running this command as a
83 local user, you may be prompted for the root password while the
84 process is running. For unsupported distributions, the depen‐
85 dency names will be displayed along with common names for the
86 package. The install-dependencies option needs to be supplied
87 with the test name or suite as an argument. When using the
88 install option, the external dependencies are automatically
89 checked.
90 make-download-cache
92 This option will create a download cache for use by the Phoronix
93 Test Suite. The download cache is created of test files already
94 downloaded to the local system. If passing any test/suite names
95 to make-download-cache, the needed files for those test profiles
96 will first be automatically downloaded before creating the
97 cache.
98 remove-installed-test [Test]
100 This option will permanently remove a installed test by the
101 Phoronix Test Suite.
102 TESTING
105 auto-compare This option will autonomously determine the most
106 relevant test(s) to run for any selected sub-system(s). The
107 tests to run are determined via OpenBenchmarking.org integration
108 with the global results pool. Related test results from Open‐
109 Benchmarking.org are also merged to provide a straight-forward
110 and effective means of carrying out a system comparison. If
111 wishing to find comparable results for any particular test pro‐
112 file(s), simply pass the test profile names as additional argu‐
113 ments to this command.
114 benchmark [Test | Suite | OpenBenchmarking ID | Test Result] ...
116 This option will install the selected test(s) (if needed) and
117 will proceed to run the test(s). This option is equivalent to
118 running phoronix-test-suite with the install option followed by
119 the run option. Multiple arguments can be supplied to run addi‐
120 tional tests at the same time and save the results into one
121 file.
122 estimate-run-time [Test | Suite | OpenBenchmarking ID | Test Result]
124 This option will provide estimates for test run-time / length.
125 finish-run [Test Result]
127 This option can be used if a test run had not properly finished
128 running all tests within a saved results file. Using this option
129 when specifying a saved results file where all tests had not
130 completed will attempt to finish testing on the remaining tests
131 where there are missing results.
132 run [Test | Suite | OpenBenchmarking ID | Test Result] ...
134 This option will run the selected test(s).
135 run-random-tests
137 This option will query OpenBenchmarking.org to run random bench‐
138 marks and result comparisons on the system. This test can be
139 used for simply supplying interesting results from your system
140 onto OpenBenchmarking.org, stressing your system with random
141 workloads, seeding new OpenBenchmarking.org results, etc. Basic
142 options are provided at start-up for tuning the randomness of
143 the testing when running this command.
144 run-tests-in-suite
146 This option can be used if you wish to run all of the tests
147 found in a supplied suite, but you wish to re-configure each of
148 the test options rather than using the defaults supplied by the
149 suite.
150 stress-batch-run [Test | Suite | OpenBenchmarking ID | Test Result] ...
152 This option will run the passed tests/suites in the multi-
153 process stress-testing mode while behaving by the Phoronix Test
154 Suite batch testing characteristics. The stress-batch-run mode
155 is similar to the stress-run command except that for any tests
156 passed to it will run all combinations of the options rather
157 than prompting the user for the values to be selected.
158 stress-run [Test | Suite | OpenBenchmarking ID | Test Result] ...
160 This option will run the passed tests/suites in the multi-
161 process stress-testing mode. The stress-run mode will not pro‐
162 duce a result file but is rather intended for running multiple
163 test profiles concurrently to stress / burn-in the system. The
164 number of tests to run concurrently can be toggled via the
165 PTS_CONCURRENT_TEST_RUNS environment variable and by default is
166 set to a value of 2.
167 strict-benchmark [Test | Suite | OpenBenchmarking ID | Test Result] ...
169 This option is equivalent to the `benchmark` option except it
170 enables various options to run benchmarks an extended number of
171 times for ensuring better statistical accuracy if enforcing
172 strict controls over the data quality, in some cases running the
173 benchmarks for 20+ times.
174 strict-run [Test | Suite | OpenBenchmarking ID | Test Result] ...
176 This option is equivalent to the `run` option except it enables
177 various options to run benchmarks an extended number of times
178 for ensuring better statistical accuracy if enforcing strict
179 controls over the data quality, in some cases running the bench‐
180 marks for 20+ times.
181 BATCH TESTING
184 batch-benchmark [Test | Suite | OpenBenchmarking ID | Test
185 Result] ... This option and its arguments are equivalent to the
186 benchmark option, but the process will be run in the Phoronix
187 Test Suite batch mode.
188 batch-install [Test | Suite | OpenBenchmarking ID | Test Result] ...
190 If you wish to run the install process in the Phoronix Test
191 Suite batch mode but do not wish to run any tests at this time.
192 Running the install process in the batch mode will use the
193 default values and not prompt the user of any possible options,
194 to ensure the process is fully automated.
195 batch-run [Test | Suite | OpenBenchmarking ID | Test Result] ...
197 This option and its arguments are equivalent to the run option,
198 but the process will be run in the Phoronix Test Suite batch
199 mode.
200 batch-setup
202 This option is used to configure the batch mode options for the
203 Phoronix Test Suite, which is subsequently written to the user
204 configuration file. Among the options are whether to automati‐
205 cally upload the test results to OpenBenchmarking.org and
206 prompting for the saved file name.
207 default-benchmark [Test | Suite | OpenBenchmarking ID | Test Result]
209 ...
210 This option will install the selected test(s) (if needed) and
211 will proceed to run the test(s) in the defaults mode. This
212 option is equivalent to running phoronix-test-suite with the
213 install option followed by the default-run option.
214 default-run [Test | Suite | OpenBenchmarking ID | Test Result] ...
216 This option will run the selected test(s). The name of the test
217 or suite must be supplied or the OpenBenchmarking.org ID or
218 saved local file name. Multiple arguments can be supplied to run
219 additional tests at the same time and save the results in a
220 suite-like fashion. Unlike the normal run option, the default-
221 run will not prompt the user to select from the available test
222 options but will instead use the default options as automati‐
223 cally set by pts-core or the test profile. Use batch-run to
224 automatically test all of the available options.
225 dry-run [Test | Suite | OpenBenchmarking ID | Test Result] ...
227 This option and its arguments pre-set the Phoronix Test Suite
228 batch run mode with enforcing of defaults to not save any
229 results and other behavior intended for a dry/test run. This
230 option is primarily intended for testing/evaluation purposes.
231 internal-run [Test | Suite | OpenBenchmarking ID | Test Result] ...
233 This option and its arguments pre-set the Phoronix Test Suite
234 batch run mode with sane values for carrying out benchmarks in a
235 semi-automated manner and without uploading any of the result
236 data to the public OpenBenchmarking.org.
237 OPENBENCHMARKING.ORG
240 clone-result [OpenBenchmarking ID] ... This option will down‐
241 load a local copy of a file that was saved to OpenBenchmark‐
242 ing.org, as long as a valid public ID is supplied.
243 list-recommended-tests
245 This option will list recommended test profiles for benchmarking
246 sorted by hardware sub-system. The recommended tests are deter‐
247 mined via querying OpenBenchmarking.org and determining the most
248 popular tests for a given environment based upon the number of
249 times a test profile has been downloaded, the number of test
250 results available on OpenBenchmarking.org for a given test pro‐
251 file, the age of the test profile, and other weighted factors.
252 make-openbenchmarking-cache
254 This option will attempt to cache the test profile/suite meta-
255 data from OpenBenchmarking.org for all linked repositories. This
256 is useful if you're going to be running the Phoronix Test Suite
257 / Phoromatic behind a firewall or without any Internet connec‐
258 tion. Those with unrestricted Internet access or not utilizing a
259 large local deployment of the Phoronix Test Suite / Phoromatic
260 shouldn't need to run this command.
261 openbenchmarking-changes
263 This option will list recent changes to test profiles of enabled
264 OpenBenchmarking.org repositories.
265 openbenchmarking-login
267 This option is used for controlling your Phoronix Test Suite
268 client options for OpenBechmarking.org and syncing the client to
269 your account.
270 openbenchmarking-refresh
272 This option is used for refreshing the stored OpenBenchmark‐
273 ing.org repostory information and other data. The Phoronix Test
274 Suite will automatically refresh this data every three days or
275 when other thresholds are exceeded, but this command can be used
276 to manually refresh/updates the data.
277 openbenchmarking-repositories
279 This option will list the OpenBenchmarking.org repositories cur‐
280 rently linked to this Phoronix Test Suite client instance.
281 openbenchmarking-uploads
283 This option will list any recent test result uploads from the
284 system's IP address to OpenBenchmarking.org.
285 recently-added-tests
287 This option will list the most recently added (newest) test pro‐
288 files.
289 upload-result [Test Result]
291 This option is used for uploading a test result to OpenBench‐
292 marking.org.
293 upload-test-profile
295 This option can be used for uploading a test profile to your
296 account on OpenBenchmarking.org. By uploading your test profile
297 to OpenBenchmarking.org, others are then able to browse and
298 access this test suite for easy distribution in a seamless man‐
299 ner by other Phoronix Test Suite clients.
300 upload-test-suite
302 This option can be used for uploading a test suite to your
303 account on OpenBenchmarking.org. By uploading your test suite to
304 OpenBenchmarking.org, others are then able to browse and access
305 this test suite for easy distribution.
306 INFORMATION
309 info [Test | Suite | OpenBenchmarking ID | Test Result] This
310 option will show details about the supplied test, suite, virtual
311 suite, or result file.
312 list-all-tests
314 This option will list all test profiles that are available from
315 the enabled OpenBenchmarking.org repositories. Unlike the other
316 test listing options, list-all-tests will show deprecated tests,
317 potentially broken tests, or other tests not recommended for all
318 environments. The only check in place is ensuring the test pro‐
319 files are at least compatible with the operating system in use.
320 list-available-suites
322 This option will list all test suites that are available from
323 the enabled OpenBenchmarking.org repositories.
324 list-available-tests
326 This option will list all test profiles that are available from
327 the enabled OpenBenchmarking.org repositories where supported on
328 the system and are of a verified state. If the system has no
329 Internet access, it will only list the test profiles where the
330 necesary test assets are available locally on the system or on
331 an available network cache (the same behavior as using the list-
332 cached-tests sub-command), unless using the list-all-tests
333 option to override this behavior.
334 list-available-virtual-suites
336 This option will list all available virtual test suites that can
337 be dynamically created based upon the available tests from
338 enabled OpenBenchmarking.org repositories.
339 list-cached-tests
341 This option will list all test profiles where any needed test
342 profiles are already cached or available from the local system
343 under test. This is primarily useful if testing offline/behind-
344 the-firewall and other use-cases where wanting to rely only upon
345 local data.
346 list-installed-dependencies
348 This option will list all of the packages / external test depen‐
349 dencies that are already installed on the system that the
350 Phoronix Test Suite may potentially depend upon by test pro‐
351 files.
352 list-installed-suites
354 This option will list all suites that are currently installed on
355 the system.
356 list-installed-tests
358 This option will list all test profiles that are currently
359 installed on the system.
360 list-missing-dependencies
362 This option will list all of the packages / external test depen‐
363 dencies that are missing from the system that the Phoronix Test
364 Suite may potentially need by select test profiles.
365 list-not-installed-tests
367 This option will list all test profiles that are supported and
368 available but presently NOT installed on the system.
369 list-possible-dependencies
371 This option will list all of the packages / external test depen‐
372 dencies that are are potentially used by the Phoronix Test
373 Suite.
374 list-saved-results
376 This option will list all of the saved test results found on the
377 system.
378 list-test-usage
380 This option will list various details about installed tests and
381 their usage.
382 list-unsupported-tests
384 This option will list all available test profiles that are
385 available from the enabled OpenBenchmarking.org repositories but
386 are NOT SUPPORTED on the given hardware/software platform. This
387 is mainly a debugging option for those looking for test profiles
388 to potentially port to new platforms, etc.
389 search This option provides command-line searching abilities for test
391 profiles / test suites / test results. The search query can be
392 passed as a parameter otherwise the user is prompted to input
393 their search query..
394 ASSET CREATION
397 build-suite This option will guide the user through the process
398 of generating their own test suite, which they can then run.
399 Optionally, passed as arguments can be the test(s) or suite(s)
400 to add to the suite to be created, instead of being prompted
401 through the process.
402 create-test-profile
404 This option can be used for creating a Phoronix Test Suite test
405 profile by answering questions about the test for constructing
406 the test profile XML meta-data and handling other boiler-plate
407 basics for getting started in developing new tests.
408 debug-benchmark [Test | Suite | OpenBenchmarking ID | Test Result] ...
410 This option is intended for use by test profile writers and is
411 identical to the <em>run</em> option but will yield more infor‐
412 mation during the run process that can be used to debug issues
413 with a test profile or to verify the test profile is functioning
414 correctly.
415 debug-install [Test | Suite | OpenBenchmarking ID | Test Result] ...
417 This option is intended for use by test profile writers and is
418 identical to the install option but will yield more information
419 during the run process that can be used to debug issues with a
420 test profile installer or to verify the test profile is func‐
421 tioning correctly.
422 debug-result-parser [Test | Suite | OpenBenchmarking ID | Test Result]
424 ...
425 This option is intended for use by test profile writers and is
426 used for debugging a result parser. No test execution is done,
427 but there must already be PTS-generated .log files present
428 within the test's installation directory.
429 debug-test-download-links [Test | Suite | OpenBenchmarking ID | Test
431 Result]
432 This option will check all download links within the specified
433 test profile(s) to ensure there are no broken URLs.
434 download-test-files [Test | Suite | OpenBenchmarking ID | Test Result]
436 ...
437 This will download the selected test file(s) to the Phoronix
438 Test Suite download cache but will not install the tests.
439 inspect-test-profile [Test]
441 This option can be used for inspecting a Phoronix Test Suite
442 test profile with providing inside details on test profiles for
443 debugging / evaluation / learning purposes.
444 result-file-to-suite [Test Result]
446 This option will guide the user through the process of generat‐
447 ing their own test suite, which they can then run, that is based
448 upon an existing test results file.
449 validate-result-file
451 This option can be used for validating a Phoronix Test Suite
452 result file as being compliant against the OpenBenchmarking.org
453 specification.
454 validate-test-profile [Test]
456 This option can be used for validating a Phoronix Test Suite
457 test profile as being compliant against the OpenBenchmarking.org
458 specification.
459 validate-test-suite
461 This option can be used for validating a Phoronix Test Suite
462 test suite as being compliant against the OpenBenchmarking.org
463 specification.
464 RESULT MANAGEMENT
467 analyze-all-runs [Test Result] This option will generate a can‐
468 dlestick graph showing the distribution of results from all
469 trial runs. The candlestick graph is similar to the Japanese
470 candlestick charts used by the financial industry, except
471 instead of representing stock data it is numerical result data
472 from all trial runs.0he tip of the upper-wick represents the
473 highest value of the test runs with the tip of the lower-wick
474 representing the lowest value of all test runs. The upper-edge
475 of the candle body represents the first or last run value and
476 the lower-edge represents the first or last run value. Lastly,
477 if the last run value is less than the first run value, the can‐
478 dle body is the same color as the graph background, otherwise
479 the last run value is greater.
480 auto-sort-result-file [Test Result]
482 This option is used if you wish to automatically attempt to sort
483 the results by their result identifier string.
484 compare-results-to-baseline [Test Result] [Test Result]
486 This option will allows you to specify a result as a baseline
487 (first parameter) and a second result file (second parameter)
488 that will offer some analysis for showing how the second result
489 compares to the first in matching tests.
490 compare-results-two-way [Test Result]
492 This option will allows you to specify a result file and from
493 there to compare two individual runs within that result file for
494 looking at wins/losses and other metrics in a head-to-head type
495 comparison.
496 edit-result-file [Test Result]
498 This option is used if you wish to edit the title and descrip‐
499 tion of an existing result file.
500 extract-from-result-file [Test Result]
502 This option will extract a single set of test results from a
503 saved results file that contains multiple test results that have
504 been merged. The user is the prompted to specify a new result
505 file name and select which result identifier to extract.
506 merge-results [Test Result] ...
508 This option will manually merge multiple sets of test results
509 generated by the Phoronix Test Suite.
510 refresh-graphs [Test Result]
512 This option will re-render and save all result graphs within a
513 saved file. This option can be used when making modifications to
514 the graphing code or its color/option configuration file and
515 testing the changes.
516 remove-result [Test Result]
518 This option will permanently remove the saved file set that is
519 set as the first argument.
520 remove-results-from-result-file [Test Result]
522 This option is used if there are test results (benchmarks) to be
523 dropped from a given result file. The user must specify a saved
524 results file and then they will be prompted to select the
525 tests/benchmarks to remove.
526 remove-run-from-result-file [Test Result]
528 This option is used if there is a set of test results you wish
529 to remove/delete from a saved results file. The user must spec‐
530 ify a saved results file and then they will be prompted to
531 select the results identifier associated with the results they
532 wish to remove.
533 rename-identifier-in-result-file [Test Result]
535 This option is used if you wish to change the name of the iden‐
536 tifier in a test results file that is shown in the Phoronix Test
537 Suite Results Viewer and the contained graphs.
538 rename-result-file [Test Result]
540 This option is used if you wish to change the name of the saved
541 name of a result file.
542 reorder-result-file [Test Result]
544 This option is used if you wish to manually change the order in
545 which test results are shown in the Phoronix Test Suite Results
546 Viewer and the contained graphs. The user must specify a saved
547 results file and then they will be prompted to select the
548 results identifiers one at a time in the order they would like
549 them to be displayed from left to right.
550 result-file-confidence [Test Result]
552 This option will read a saved test results file and display var‐
553 ious statistics on the confidence of the results with the stan‐
554 dard deviation, three-sigma values, and other metrics while
555 color-coding "passing" results in green.
556 result-file-raw-to-csv [Test Result]
558 This option will read a saved test results file and output the
559 raw result file run data to a CSV file. This raw (individual)
560 result file output is intended for data analytic purposes where
561 the result-file-to-csv is more end-user-ready.
562 result-file-stats [Test Result]
564 This option is used if you wish to analyze a result file by see‐
565 ing various statistics on the result data for result files con‐
566 taining at least two sets of data.
567 result-file-to-csv [Test Result]
569 This option will read a saved test results file and output the
570 system hardware and software information along with the results
571 to a CSV output. The CSV (Comma Separated Values) output can
572 then be loaded into a spreadsheet for easy viewing.
573 result-file-to-json [Test Result]
575 This option will read a saved test results file and output the
576 basic result information to JSON (JavaScript Object Notation).
577 result-file-to-pdf [Test Result]
579 This option will read a saved test results file and output the
580 system hardware and software information along with the results
581 to a PDF file.
582 result-file-to-text [Test Result]
584 This option will read a saved test results file and output the
585 system hardware and software information to the terminal. The
586 test results are also outputted.
587 show-result [Test Result]
589 Open up the test results in the Phoronix Test Suite Result
590 Viewer or on OpenBenchmarking.org.
591 wins-and-losses [Test Result]
593 This option is used if you wish to analyze a result file to see
594 which runs produced the most wins/losses of those result identi‐
595 fiers in the saved file.
596 OTHER
599 commands This option will display a short list of possible
600 Phoronix Test Suite commands.
601 debug-dependency-handler
603 This option is used for testing the distribution-specific depen‐
604 dency handler for external dependencies.
605 debug-render-test
607 This option is used during the development of the Phoronix Test
608 Suite software for testing of the result and graph rendering
609 code-paths This option will download a large number of reference
610 test results from LinuxBenchmarking.com.
611 debug-self-test
613 This option is used during the development of the Phoronix Test
614 Suite software for testing of internal interfaces, commands, and
615 other common code-paths. The produced numbers should only be
616 comparable for the same version of the Phoronix Test Suite, on
617 the same hardware/software system, conducted on the same day of
618 testing. This isn't intended as any scientific benchmark but
619 simply to stress common PHP code-paths and looking for hot areas
620 to optimize, etc.
621 help This option will display a list of available Phoronix Test Suite
623 commands and possible parameter types.
624 version
626 This option will display the Phoronix Test Suite client version.
627 MODULES
630 auto-load-module This option can be used for easily adding a
631 module to the AutoLoadModules list in the Phoronix Test Suite
632 user configuration file. That list controls what PTS modules are
633 automatically loaded on start-up of the Phoronix Test Suite.
634 list-modules
636 This option will list all of the available Phoronix Test Suite
637 modules on this system.
638 module-info [Phoronix Test Suite Module]
640 This option will show detailed information on a Phoronix Test
641 Suite module such as the version, developer, and a description
642 of its purpose.
643 module-setup [Phoronix Test Suite Module]
645 This option will allow you to configure all available end-user
646 options for a Phoronix Test Suite module. These options are then
647 stored within the user's configuration file. Not all modules may
648 have options that can be configured by the end-user.
649 test-module [Phoronix Test Suite Module]
651 This option can be used for debugging a Phoronix Test Suite mod‐
652 ule.
653 unload-module
655 This option can be used for easily removing a module from the
656 AutoLoadModules list in the Phoronix Test Suite user configura‐
657 tion file. That list controls what modules are automatically
658 loaded on start-up of the Phoronix Test Suite.
659 USER CONFIGURATION
662 enterprise-setup This option can be run by enterprise users
663 immediately after package installation or as part of an in-house
664 setup script. Running this command will ensure the phoronix-
665 test-suite program is never interrupted on new runs to accept
666 user agreement changes and defaults the anonymous usage report‐
667 ing to being disabled and other conservative defaults.
668 network-info
670 This option will print information detected by the Phoronix Test
671 Suite around the system's network configuration.
672 network-setup
674 This option allows the user to configure how the Phoronix Test
675 Suite connects to OpenBenchmarking.org and other web-services.
676 Connecting through an HTTP proxy can be configured through this
677 option.
678 user-config-reset
680 This option can be used for resetting the Phoronix Test Suite
681 user configuration file to its default state.
682 user-config-set
684 This option can be used for setting an XML value in the Phoronix
685 Test Suite user configuration file.
686 PHOROMATIC
689 start-phoromatic-server Start the Phoromatic web server for con‐
690 trolling local Phoronix Test Suite client systems to facilitate
691 automated and repeated test orchestration and other automated
692 features targeted at the enterprise.
693 RESULT VIEWER
696 n _
697 SEE ALSO
700 Websites:
701 https://www.phoronix-test-suite.com/
702 https://commercial.phoronix-test-suite.com/
703 https://www.openbenchmarking.org/
704 https://www.phoronix.com/
705 https://www.phoronix.com/forums/
706
708 Copyright 2008 - 2019 by Phoronix Media, Michael Larabel.
709