phodevi: Fill in some Windows gaps

[phoromatic] Fix set context call

AUTHORS

@@ -1,4 +1,4 @@
-Copyright 2008 - 2020 by Phoronix Media.
+Copyright 2008 - 2021 by Phoronix Media.
 
 Lead Architects:
 

ChangeLog

@@ -1,5 +1,231 @@
 PHORONIX TEST SUITE CHANGE-LOG
 
+Phoronix Test Suite 10.4.0
+16 May 2021
+
+pts-core: Ubuntu 21.04 dependency updates for changed/removed package names
+pts-core: Add "auto-resolution-wide" option
+pts-core: Add $CPU_THREADS_PER_CORE helper
+pts-core: Allow perf-per-dollar-per-hour in the result viewer, extending perf-per-dollar HTML helper
+pts-core: Add PTS_EXTRA_SYSTEM_LOGS_DIR environment variable to allow pointing to directory of extra system log files
+pts-core: Add RepositoryURL option for test profiles
+phodevi: Intel Linux graphics string format improvement
+phoromatic: Treat set context scripts as a file rather than executing it as a buffer
+phoromatic: Allow passing Phodevi system properties to Phoromatic Server
+phodevi: Add some new properties, port some pts_network info to phodevi interfaces
+system_monitor: Adjust perf-per precision
+
+Phoronix Test Suite 10.4.0 Milestone 1
+17 March 2021
+
+pts-core: Optimize out sorting percentile values array excess times
+pts-core: Optimization to avoid re-parsing test profile definition multiple times
+pts-core: Optimization to avoid re-parsing installed test metadata multiple times
+pts-core: Allow longer HTTP timeouts on OpenBenchmarking.org result uploads if needed
+pts-core: Allow sorting runs within a result file from within the result viewer web interface
+
+Phoronix Test Suite 10.2.2
+17 February 2021
+
+pts-core: Add helper text when hitting a download with no working mirrors
+pts-core: Various external dependency updates
+pts-core: Add enable-repo sub-command for more easily enabling new OpenBenchmarking.org repos
+pts-core: Result viewer fix for the limit drop down menu potentially not being activated in some cases
+pts-core: Allow renaming runs within the result viewer
+phoromatic: Ensure pcntl_signal is present before starting Phoromatic Server
+phoromatic: PHP 8 compatibility fixes
+phodevi: Fix display driver name potentially being reported inaccurate for some obscure graphics cards / driver configurations
+phodevi: Export current GPU graphics card PCI device ID (GPU_DEVICE_ID) for some games/tests relying on it for configuration
+
+Phoronix Test Suite 10.2.1
+1 February 2021
+
+pts-core: Add "InstallRequiresInternet" option for test profiles that is more narrow (install time only) than the existing "RequiresInternet"
+pts-core: Add check-tests sub-command
+pts-core: Fix possible crash on PDF output
+pts-core: Various small fixes and tweaks
+pts-core: Fix PHP8 + cURL download error
+pts_Graph: A number of minor SVG standards compliance updates
+phodevi: Log Transparent Huge Pages setting as part of system details
+phodevi: Don't bother parsing the X.org log if it grows too big
+
+Phoronix Test Suite 10.2.0
+5 January 2021
+
+pts-core: PHP8 detection improvements
+pts-core: For estimated run time, avoid over-calculating time if test has no options but multiple outputs
+pts-core: Updated (Open)Mandriva external dependencies
+pts_Graph: Minor enhancements
+phodevi: Add support for reporting ACPI Platform Profile and INT340x Workload Hint
+
+Phoronix Test Suite 10.2.0 Milestone 3
+21 December 2020
+
+pts-core: Add debug-unhandled-dependencies option
+pts-core: Default to 2.5% std dev threshold default on new installs
+pts-core: BSD external dependency updates
+pts-core: Various refinements to the text user interface
+pts-core: When a test profile hits a failed download / broken mirror, report that URL to OpenBenchmarking.org
+phodevi: Don't restore the Phodevi cache if the /etc/machine-id changed (or /etc/hostname as fallback)
+
+Phoronix Test Suite 10.2.0 Milestone 2
+6 December 2020
+
+pts-core: Transition to new JSON-based data format for managing test install metadata while maintaining backwards compatibility with prior XML format
+pts-core: Begin tracking test run-times per-hash (all configured test options) for more detailed time tracking and in turn time estimates on subsequent runs
+pts-core: Increase compression factor when uploading benchmark results
+pts-core: Last minute fixes for PHP 8.0 compatibility
+phodevi: Report if CPUFreq Boost enabled/disabled
+turbostat: Add TurboStat module to easily generate turbostat dumps on a per-test basis to log files
+phoromatic: Much faster web viewer performance especially with large databases
+
+Phoronix Test Suite 10.2.0 Milestone 1
+21 November 2020
+
+pts-core: Log lock_stat, config.gz, dmidecode to system logs
+pts-core: Only show Apple options when running on macOS
+pts-core: Add extra safeguard around FORCE_TIMES_TO_RUN for disabling dynamic run count
+ob_auto_compare: Intelligently choose more relevant reference results
+phodevi: macOS CPU temperature monitoring support
+phodevi: Support for reading WattsUp Pro power meter data directly without utility using WATTS_UP_METER=<USB TTY>
+phodevi: Report Google Compute Engine machine type as part of motherboard string
+phodevi: Add dumpe2fs to system logs when running on EXT4 and root
+phodevi: Add block size reporting
+phodevi: CPU power reporting for Ampere Altra
+phodevi: Various Ampere Altra hardware detection/reporting improvements
+phodevi: Support reading CPU package power consumption on macOS using powermetrics
+
+Phoronix Test Suite 10.0.1
+21 October 2020
+
+pts-core: Fix for older versions of PHP such as in RHEL7
+pts-core: Add Thermald version reporting to system table when active
+phodevi: Detection improvements for new CPUs
+phodevi: Avoid "11th Gen Intel" CPU string
+phodevi: Update for NVMe drive reporting with KIOXIA, Toshiba sometimes not reporting their brand first
+
+Phoronix Test Suite 10.0.0
+13 October 2020
+
+pts-core: Ensure any post-run script is triggered still under halt-testing/skip-test conditions
+pts-core: Allow batch processing of performance per dollar metrics
+phodevi: Add Intel AMX presence detection
+phodevi: Add detection for Intel Alder Lake, Jasper Lake, Sapphire Rapids, and others
+phoromatic: Ensure Windows tests get displayed even if running the Phoromatic Server on Linux
+flush_caches: Add module to flush system caches between runs
+test_timeout: Add module to quit a test run if it exceeds a predefined time limit or 'auto' determination
+
+Phoronix Test Suite 10.0.0 Milestone 3
+1 October 2020
+
+pts-core: Don't show Vulkan options if Vulkan support is known to be unavailable/broken
+pts-core: Add OptionSelect tag support within test suite definitions
+pts-core: Allow * wildcard match in FileCheck handling within external dependency XML
+pts-core: Add "OS" TestType
+pts-core: Various external dependency updates
+pts-core: Continued tweaking to the analytics engine
+phodevi: Add Neoverse N2, Cortex-X1 detection and other Arm CPU updates
+pts_Graph: Various improvements
+
+Phoronix Test Suite 10.0.0 Milestone 2
+12 September 2020
+
+pts-core: Honor NO_COLOR environment variable for disabling terminal coloring
+pts-core: Allow launching just the result viewer from systemd (phoronix-result-server.service)
+pts-core: Result viewer UI tweaks
+pts-core: Minor fixes
+pts-core: Add RequiresRootInstall test profile option
+pts-core: Result file text output tweaks
+pts-core: More robust test result parsing in certain time formats
+
+Phoronix Test Suite 10.0.0 Milestone 1
+19 August 2020
+
+pts-core: Add keep-results-in-result-file sub-command
+pts-core: Split the dynamic result viewer into its own embed class for result file handling to allow for easy re-use by OpenBenchmarking, Phoromatic, etc
+pts-core: Various changes for supporting the new OpenBenchmarking.org infrastructure
+pts_Graph: Add histogram type
+phodevi: CPU core name / family detection to friendly strings (OpenBenchmarking.org driven)
+phodevi: Report core name via system-info command
+phodevi: Various storage HDD/SSD detection reporting improvements
+phodevi: Ampere Altra detection
+phodevi: macOS/Apple hardware detection improvements
+
+Phoronix Test Suite 9.8.0
+9 July 2020
+
+pts-core: Handling of cases where all options are unsupported (such as CUDA and OpenCL tests with no valid backends found) to avoid prompts
+pts-core: Be more liberal in allowing CUDA/OpenCL GPU compute tests to run fine without display server active
+pts-core: Fix for not filling test suites of contained tests in some select cases (sub-suites listing in results viewer)
+pts-core: Allow creating new virtual test suites that are not prefixed by a OB repository
+phodevi: NVIDIA GPU detection within WSL2
+docker: Rewritten phoronix/pts Docker implementation based on Ubuntu 20.04 LTS
+
+Phoronix Test Suite 9.8.0 Milestone 2
+24 June 2020
+
+pts-core: Add client side plumbing for estimated test install time from OpenBenchmarking.org
+pts-core: Add estimate-install-time sub-command, show estimated install time when installing a test
+pts-core: Improve web browser selection logic for result viewer
+pts-core: Add search field to the result viewer areas for limiting based on title/argument matching
+pts-core: Various minor fixes
+pts-core: Don't show OpenCL test options if no OpenCL drivers/adapters appear present
+phodevi: Fix for incorrect monitor count when parsing X.Org log
+phodevi: Warning fixes for latest WSL
+
+Phoronix Test Suite 9.8.0 Milestone 1
+3 June 2020
+
+pts-core: When an install fails, try a newer minor version update to that test profile if available (fixes broken download mirrors, etc)
+pts-core: When a newer minor version of a test profile is installed and a requested (older) one is not, use the newer compatible version
+pts-core: Rewrite virtual test suite implementation
+pts-core: Add handler for ensuring reported system time is accurate, otherwise calculate current date/time using offsets
+pts-core: When scanning test suites on disk, ensure the latest test suite version is used
+pts-core: Add test-to-suite-map sub-command
+pts-core: Fix for loading the result viewer JavaScript / CSS when running on a Windows host
+pts-core: For tests requiring root but not run initially as root and using monitoring data, drop the first run to ensure sudo promot doesn't skew time
+pts-core: Fix PHP8 error in the 'info' sub-command
+pts-core: Other PHP deprecation code tweaks
+phodevi: Add amd_energy Linux driver support
+
+Phoronix Test Suite 9.6.1
+25 May 2020
+
+pts-core: Show unit/scale in CSV export
+pts-core: When limiting results to show in result viewer, keep child objects that match the desired type for the parent
+pts-core: Add rebuild-test-suite option for regenerating suite XML all cleaned up
+pts-core: Allow exporting result files to XML test suites via the result viewer
+linux_perf: Reporting many more events
+pts-core: External dependency updates
+pts_Graph: graph code tweaks
+phodevi: Avoid macOS reporting X-Core string before Intel CPU string
+phodevi: Sway compositor version detection
+phodevi: Detection of newer Arm CPU cores
+
+Phoronix Test Suite 9.6.0
+21 April 2020
+
+pts-core: Allow building virtual suites off external dependencies
+pts-core: Various result viewer improvements
+pts-core: Allow saving results under stress-run
+pts-core: Responsive/mobile result viewer improvements
+pts-core: Show local tests within the build-suite sub-command
+pts-core: Show local suites within the list-installed-suites sub-command
+pts_Graph: Restore capability for drawing mini graphs for all results in a result file overview
+
+Phoronix Test Suite 9.6.0 Milestone 3
+12 April 2020
+
+pts-core: Allow automated per-thread/core/clock/RAM graphs within the result viewer
+pts-core: Result viewer add "Limit displaying results to tests within:"
+pts-core: From the result viewer allow "Show Geometric Means Per-Suite/Category"
+pts-core: Add workload-topology sub-command
+pts-core: Allow adding deprecated tests to build-suite
+pts-core: CSV export improvements
+pts-core: Add "Do Not Show Results With Incomplete Data" to the result viewer
+pts-core: Allow test suite "Status" tag
+pts-core: Don't report OB updates on deprecated tests or suites
+
 Phoronix Test Suite 9.6.0 Milestone 2
 5 April 2020
 

README.md

@@ -1,4 +1,4 @@
-# Phoronix Test Suite 9.6.0m2
+# Phoronix Test Suite 10.4.0
 https://www.phoronix-test-suite.com/
 
 The **Phoronix Test Suite** is the most comprehensive testing and benchmarking

deploy/docker/ubuntu-pts-docker-build.sh

@@ -0,0 +1,56 @@
+#!/bin/bash
+
+export TESTS_TO_PRECACHE=""
+
+# Ensure Docker on system
+DIR_NAME=phoronix-pts-docker
+mkdir -p ./$DIR_NAME/base/
+OS_OUTER=`pwd`
+cd $DIR_NAME/base
+OS_ROOT_PATH=`pwd`
+
+rm -rf phoronix-test-suite/
+git clone https://github.com/phoronix-test-suite/phoronix-test-suite.git
+cd phoronix-test-suite
+rm -rf .git
+
+# cache OpenBenchmarking.org metadata
+export PTS_USER_PATH_OVERRIDE=$OS_ROOT_PATH/var/lib/phoronix-test-suite/
+rm -f $PTS_USER_PATH_OVERRIDE
+mkdir -p $PTS_USER_PATH_OVERRIDE
+./phoronix-test-suite make-openbenchmarking-cache lean
+
+# cache select tests
+export PTS_DOWNLOAD_CACHE_OVERRIDE=$OS_ROOT_PATH/var/cache/phoronix-test-suite/download-cache/
+mkdir -p $PTS_DOWNLOAD_CACHE_OVERRIDE
+export PTS_DOWNLOAD_CACHING_PLATFORM_LIMIT=1
+# ./phoronix-test-suite make-download-cache $TESTS_TO_PRECACHE
+# ./phoronix-test-suite info 1809091-PTS-CLEARLIN01
+
+rm -f $PTS_USER_PATH_OVERRIDE/core.pt2so
+
+# cleanup
+cd $OS_OUTER/$DIR_NAME
+
+tar -C base -cf base.tar .
+rm -f base.tar.xz
+xz -v -T0 base.tar
+
+cat > Dockerfile << EOF
+FROM ubuntu:20.04
+MAINTAINER Phoronix Media <commercial@phoronix-test-suite.com>
+ADD base.tar.xz /
+ARG DEBIAN_FRONTEND=noninteractive
+RUN apt update
+RUN apt install -y unzip php-cli apt-utils mesa-utils php-xml git-core apt-file
+RUN apt-file update
+CMD ["/phoronix-test-suite/phoronix-test-suite", "shell"]
+EOF
+
+docker build -t $DIR_NAME .
+
+# docker run -it phoronix-pts-docker
+
+# docker tag phoronix-pts-docker phoronix/pts
+# docker push phoronix/pts
+

deploy/farm-system-customizations/intel-xorg-headless.conf

@@ -1,27 +0,0 @@
-Section "Monitor"
-    Identifier             "Monitor0"
-    Modeline "1920x1080" 174.83 1920 2056 2248 2536 1080 1081 1084 1149             # 174.83 MHz,  68.94 kHz,  60.00 Hz
-    Option      "PreferredMode"  "1920x1080"
-        Option "Enable" "true"
-EndSection
-
-Section "Device"
-    Identifier             "Device0"
-    Driver                 "intel" #Choose the driver used for this monitor
-        Option "DDC" "0"
-        Option "Virtualheads" "1"
-        Option "Vsync" "0"
-        Option "SwapbuffersWait" "0"
-	Option "DRI" "3"
-EndSection
-
-Section "Screen"
-    Identifier             "Screen0"  #Collapse Monitor and Device section to Screen section
-    Device                 "Device0"
-    Monitor                "Monitor0"
-    DefaultDepth           24 #Choose the depth (16||24)
-    SubSection             "Display"
-        Depth              24
-        Modes              "1920x1080" #Choose the resolution
-    EndSubSection
-EndSection

deploy/farm-system-customizations/radeon-xorg-headless.conf

@@ -1,23 +0,0 @@
-Section "Device"
-    Identifier             "Device0"
-    Driver                 "radeon"
-	Option "SwapBuffersWait" "0"
-		Option "DRI "3"
-EndSection
-
-Section "Monitor"
-    Identifier             "Monitor0"
-        Option "enable" "true"
-     Modeline "1920x1080" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
-EndSection
-
-Section "Screen"
-        Identifier "Fake"
-        Device "Device0"
-        Monitor "Monitor0"
-        Option "ConnectedMonitor" "Monitor0"
-        SubSection "Display"
-                Depth 24
-                Modes "1920x1080"
-        EndSubSection
-EndSection

deploy/farm-system-customizations/ubuntu-initial-setup.sh

@@ -1,10 +0,0 @@
-#!/bin/sh
-
-sudo apt-get install openssh-server git-core php5-cli
-
-echo "GRUB_RECORDFAIL_TIMEOUT=0" >> /etc/default/grub
-update-grub
-
-sudo passwd
-
-# check if needing "tty -s &&" for auto log-in user in ~/.profile

deploy/phoromatic-systemd/phoronix-result-server.service

@@ -0,0 +1,14 @@
+[Unit]
+Description=Phoronix Test Suite Result viewer
+After=syslog.target network.target
+Documentation=man:phoronix-test-suite(1)
+
+[Service]
+TimeoutStartSec=300
+ExecStart=/usr/bin/phoronix-test-suite start-result-viewer daemon
+Restart=on-failure
+
+[Install]
+WantedBy=multi-user.target
+
+

documentation/man-pages/phoronix-test-suite.1

@@ -1,4 +1,4 @@
-.TH phoronix-test-suite 1  "www.phoronix-test-suite.com" "9.6.0m2"
+.TH phoronix-test-suite 1  "www.phoronix-test-suite.com" "10.4.0"
 .SH NAME
 phoronix-test-suite \- The Phoronix Test Suite is an extensible open-source platform for performing testing and performance evaluation.
 .SH SYNOPSIS
@@ -25,6 +25,9 @@ A simple text-driven shell interface / helper to the Phoronix Test Suite. Ideal
 .B system-info
 Display the installed system hardware and software information as detected by the Phoronix Test Suite Phodevi Library.
 .TP
+.B system-properties
+Display various hardware/software system properties detected by the Phoronix Device Interface (Phodevi) library.
+.TP
 .B system-sensors
 Display the installed system hardware and software sensors in real-time as detected by the Phoronix Test Suite Phodevi Library.
 .TP
@@ -48,6 +51,9 @@ This option will permanently remove a installed test by the Phoronix Test Suite.
 .B benchmark [Test | Suite | OpenBenchmarking ID | Test Result]  ...
 This option will install the selected test(s) (if needed) and will proceed to run the test(s). This option is equivalent to running phoronix-test-suite with the install option followed by the run option. Multiple arguments can be supplied to run additional tests at the same time and save the results into one file.
 .TP
+.B estimate-install-time [Test | Suite | OpenBenchmarking ID | Test Result]
+This option will provide estimates for test install/setup time length.
+.TP
 .B estimate-run-time [Test | Suite | OpenBenchmarking ID | Test Result]
 This option will provide estimates for test run-time / length.
 .TP
@@ -107,6 +113,9 @@ This option and its arguments pre-set the Phoronix Test Suite batch run mode wit
 .B clone-result [OpenBenchmarking ID]  ...
 This option will download a local copy of a file that was saved to OpenBenchmarking.org, as long as a valid public ID is supplied.
 .TP
+.B enable-repo
+This option is used if wanting to add a new OpenBenchmarking.org account/repository to your system for enabling third-party/unofficial test profiles and test suites.
+.TP
 .B list-recommended-tests
 This option will list recommended test profiles for benchmarking sorted by hardware sub-system. The recommended tests are determined via querying OpenBenchmarking.org and determining the most popular tests for a given environment based upon the number of times a test profile has been downloaded, the number of test results available on OpenBenchmarking.org for a given test profile, the age of the test profile, and other weighted factors.
 .TP
@@ -141,6 +150,9 @@ This option can be used for uploading a test profile to your account on OpenBenc
 This option can be used for uploading a test suite to your account on OpenBenchmarking.org. By uploading your test suite to OpenBenchmarking.org, others are then able to browse and access this test suite for easy distribution.
 .TP
 .SH INFORMATION
+.B check-tests [Test]
+This option will perform a check on one or more test profiles to determine if there have been any vendor changes to the filename, filesize, url location, md5 and sha256 checksums.
+.TP
 .B info [Test | Suite | OpenBenchmarking ID | Test Result]
 This option will show details about the supplied test, suite, virtual suite, or result file.
 .TP
@@ -192,6 +204,9 @@ This option will list all available test profiles that are available from the en
 .B search
 This option provides command-line searching abilities for test profiles / test suites / test results. The search query can be passed as a parameter otherwise the user is prompted to input their search query..
 .TP
+.B test-to-suite-map
+This option will list all test profiles and any test suites each test belongs to.
+.TP
 .SH ASSET CREATION
 .B build-suite
 This option will guide the user through the process of generating their own test suite, which they can then run. Optionally, passed as arguments can be the test(s) or suite(s) to add to the suite to be created, instead of being prompted through the process.
@@ -217,6 +232,9 @@ This will download the selected test file(s) to the Phoronix Test Suite download
 .B inspect-test-profile [Test]
 This option can be used for inspecting a Phoronix Test Suite test profile with providing inside details on test profiles for debugging / evaluation / learning purposes.
 .TP
+.B rebuild-test-suite [Suite]
+This option will regenerate the local test suite XML file against the OpenBenchmarking.org specification. This can be used to clean up any existing XML syntax / styling issues, etc.
+.TP
 .B result-file-to-suite [Test Result]
 This option will guide the user through the process of generating their own test suite, which they can then run, that is based upon an existing test results file.
 .TP
@@ -248,12 +266,12 @@ This option is used if you wish to edit the title and description of an existing
 .B extract-from-result-file [Test Result]
 This option will extract a single set of test results from a saved results file that contains multiple test results that have been merged. The user is the prompted to specify a new result file name and select which result identifier to extract.
 .TP
+.B keep-results-in-result-file [Test Result]
+This option is the inverse of the remove-results-from-result-file sub-command. If you wish to remove all results but those listed from a given result file, this option can be used. The user must specify a saved results file and then they will be prompted to provide a string to search for in keeping those results in that given result file but removing all other data.
+.TP
 .B merge-results [Test Result]  ...
 This option will manually merge multiple sets of test results generated by the Phoronix Test Suite.
 .TP
-.B refresh-graphs [Test Result]
-This option will re-render and save all result graphs within a saved file. This option can be used when making modifications to the graphing code or its color/option configuration file and testing the changes.
-.TP
 .B remove-result [Test Result]
 This option will permanently remove the saved file set that is set as the first argument.
 .TP
@@ -293,6 +311,9 @@ This option will read a saved test results file and output the system hardware a
 .B show-result [Test Result]
 Open up the test results in the Phoronix Test Suite Result Viewer or on OpenBenchmarking.org.
 .TP
+.B workload-topology [Test Result]
+This option will read a saved test results file and print the test profiles contained within and their arrangement within different test suites for getting an idea as to the workload topology/make-up / logical groupings of the benchmarks being run.
+.TP
 .SH OTHER
 .B commands
 This option will display a short list of possible Phoronix Test Suite commands.
@@ -312,22 +333,6 @@ This option will display a list of available Phoronix Test Suite commands and po
 .B version
 This option will display the Phoronix Test Suite client version.
 .TP
-.SH RESULT ANALYSIS
-.B analyze-all-runs [Test Result]
-This option will generate a candlestick graph showing the distribution of results from all trial runs. The candlestick graph is similar to the Japanese candlestick charts used by the financial industry, except instead of representing stock data it is numerical result data from all trial runs.\n\nThe tip of the upper-wick represents the highest value of the test runs with the tip of the lower-wick representing the lowest value of all test runs. The upper-edge of the candle body represents the first or last run value and the lower-edge represents the first or last run value. Lastly, if the last run value is less than the first run value, the candle body is the same color as the graph background, otherwise the last run value is greater.
-.TP
-.B executive-summary [Test Result]
-This option will attempt to auto-generate a textual executive summary for a result file to highlight prominent results / averages.
-.TP
-.B result-file-confidence [Test Result]
-This option will read a saved test results file and display various statistics on the confidence of the results with the standard deviation, three-sigma values, and other metrics while color-coding "passing" results in green.
-.TP
-.B result-file-stats [Test Result]
-This option is used if you wish to analyze a result file by seeing various statistics on the result data for result files containing at least two sets of data.
-.TP
-.B wins-and-losses [Test Result]
-This option is used if you wish to analyze a result file to see which runs produced the most wins/losses of those result identifiers in the saved file.
-.TP
 .SH MODULES
 .B auto-load-module
 This option can be used for easily adding a module to the AutoLoadModules list in the Phoronix Test Suite user configuration file. That list controls what PTS modules are automatically loaded on start-up of the Phoronix Test Suite.
@@ -363,6 +368,19 @@ This option can be used for resetting the Phoronix Test Suite user configuration
 .B user-config-set
 This option can be used for setting an XML value in the Phoronix Test Suite user configuration file.
 .TP
+.SH RESULT ANALYSIS
+.B executive-summary [Test Result]
+This option will attempt to auto-generate a textual executive summary for a result file to highlight prominent results / averages.
+.TP
+.B result-file-confidence [Test Result]
+This option will read a saved test results file and display various statistics on the confidence of the results with the standard deviation, three-sigma values, and other metrics while color-coding "passing" results in green.
+.TP
+.B result-file-stats [Test Result]
+This option is used if you wish to analyze a result file by seeing various statistics on the result data for result files containing at least two sets of data.
+.TP
+.B wins-and-losses [Test Result]
+This option is used if you wish to analyze a result file to see which runs produced the most wins/losses of those result identifiers in the saved file.
+.TP
 .SH PHOROMATIC
 .B start-phoromatic-server
 Start the Phoromatic web server for controlling local Phoronix Test Suite client systems to facilitate automated and repeated test orchestration and other automated features targeted at the enterprise.
@@ -382,7 +400,6 @@ https://www.openbenchmarking.org/
 .br
 https://www.phoronix.com/
 .br
-https://www.phoronix.com/forums/
 .SH AUTHORS
-Copyright 2008 - 2020 by Phoronix Media, Michael Larabel.
+Copyright 2008 - 2021 by Phoronix Media, Michael Larabel.
 .TP

documentation/phoromatic.html

@@ -1,90 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<Title>Phoronix Test Suite Phoromatic</Title>
-</head>
-<body>
-<h1>Phoromatic Server</h1>
-<h2>Introduction</h2>
-<p>Phoromatic is a remote management system for the Phoronix Test Suite. Phoromatic allows the automatic (hence the name <em>Phoro-matic</em>) scheduling of tests, remote installation of new tests, and the management of multiple test systems all through an intuitive, easy-to-use web interface. Tests can be scheduled to automatically run on a routine basis across multiple test systems. The test results are then available from this central, secure location.</p>
-<p>Phoromatic was originally introduced with Phoronix Test Suite 2.0 via Phoromatic.com as a project going back to 2008~2009. Phoromatic.com debuted as a hosted instance with the option of behind-the-firewall licensing for use within organizations. With Phoronix Test Suite 5.2 the model shifted to offer a local, open-source version of Phoromatic built into the Phoronix Test Suite code-base. Thanks to continued enterprise development, with Phoronix Test Suite 5.4 is now a fully-functioning, built-in version of Phoromatic that's open-source and can be used for behind-the-firewall testing without needing to push results to OpenBenchmarking.org and the ability to keep all results private.</p>
-<p>Phoromatic in Phoronix Test Suite 5.4 also has the ability to support zero-conf  network discovery using Avahi and the automatic distribution of needed test profiles/suites and test files. Phoronix Test Suite 5.4's Phoromatic is a significant breakthrough for open-source testing particularly those running this GPL benchmarking software within test labs and other large organizations.</p>
-<h2>Features</h2>
-<p>Built atop the Phoronix Test Suite, Phoromatic offers many features for both enterprise and community/personal users:</p>
-<h3>Automated Scheduling</h3>
-<p>Whether it is every evening at 6:00PM, once every Thursday at 10:00AM or somewhere in between, Phoromatic can schedule tests to be run at user-defined intervals. The testing schedules can be updated through Phoromatic web interface. After the test(s) have run, the results will be immediately uploaded to Phoromatic.</p>
-<h3>Extensible</h3>
-<p>Any test profile or test suite that is compliant with the Phoronix Test Suite specification will work with Phoromatic. Phoromatic is able to leverage the hundreds of test profiles and test suites currently in the Phoronix Test Suite via OpenBenchmarking.org, along with any custom or proprietary test profiles you or your company utilize. Additionally, the Phoromatic interface allows the user to construct their own test suite(s).</p>
-<h3>Remote Testing</h3>
-<p>Once the test system is setup, all testing and management of that system can be done remotely. There is no need to execute Phoronix Test Suite commands locally using the GUI or command line version, but instead nearly all of the same features are accessible from the Phoromatic interface.</p>
-<h3>Multi-System Support</h3>
-<p>A single Phoromatic account is able to manage multiple test systems running the Phoronix Test Suite. Phoromatic supports grouping together test systems, tagging, and other features to support effectively managing many test systems. From the Phoromatic interface, installed system hardware and software from a given system can also be viewed.</p>
-<h3>Turn-Key Deployment</h3>
-<p>No additional software needs to be installed to support Phoromatic; all that's needed is Phoronix Test Suite 5.4 or later for full compatibility. New test systems can easily be synced with a given Phoromatic account by running a single command from the Phoronix Test Suite client.</p>
-<h3>Result Management</h3>
-<p>Test results are automatically uploaded to the Phoromatic account and remain private unless you opt to upload them to OpenBenchmarking.org. From the Phoromatic interface, results from multiple test systems can easily be compared and multiple results from the same systems can be used to track performance over time. There are also options to look at the statistical significance of the results and other features to efficiently and effectively analyze the system's performance.</p>
-<h3>Decentralized</h3>
-<p>Once the Phoronix Test Suite running on the Phoromatic Server has been able to cache all of the OpenBenchmarking.org test files and the needed files for each test, Phoromatic with any Phoronix Test Suite clients on your LAN can run fully decentralized without the need for a constant stream of OpenBenchmarking.org communication or Internet connection for that matter. (The only exception would be if your local systems don't have all their needed external dependencies and your system's package manager would need to install components like a compiler or necessary system libraries.</p>
-<h3>Fully Open-Source</h3>
-<p>Phoromatic is now fully open-source within the Phoronix Test Suite code-base for fostering greater development and new capabilities. Patches are welcome and Phoronix Media is available to provide commercial support and custom engineering services around Phoromatic and the Phoronix Test Suite.</p>
-<h2>Phoromatic Server Setup</h2>
-<p>Phoromatic is built into the Phoronix Test Suite code-base and should be found in all packaged versions of the <strong>phoronix-test-suite</strong>. Starting the Phoromatic Server entails running phoronix-test-suite start-phoromatic-server after configuring the server information within <em>~/.phoronix-test-suite/user-config.xml</em>. The Phoromatic Server can with or without root permissions depending upon your firewall and the port numbers you wish to use for the server.</p>
-<p>On the "client side", any up-to-date version of the Phoronix Test Suite can automatically communicate with the Phoromatic Server. If Avahi support is available (commonly in Linux distribution repositories as <u>avahi-tools</u>), there should be zero-conf discovery if the Phoromatic Server and client systems are on the same LAN. If a Phoronix Test Suite client discovers a Phoromatic Server, it will attempt to use it automatically as a local download cache. In the event of no Internet connection, it will also attempt to obtain the needed OpenBenchmarking.org test/suite meta-data from the Phoromatic Server based upon its archived meta-data. This allows the Phoronix Test Suite / Phoromatic deployment on the LAN to be self-sustaining without an Internet connection as long as the systems have all installed test dependencies.</p>
-<p>Further configuration of the setup parameters for the Phoromatic Server and Phoronix Test Suite clients can be tuned via the <em>~/.phoronix-test-suite/user-config.xml</em> file. All control and configuration of the Phoromatic Server is done via the web-based interface when the Phoromatic Server is active.</p>
-<p>The Phoromatic Server utilizes PHP/HHVM's built-in web-server capabilities and there's also a Phoronix Test Suite built-in WebSocket server that's also initiated for back-end processing. At this time there are no ports set by default for these services but must be defined within the user configuration file. With the Avahi zero-conf network discovery and other automated detection in place, there's little restrictions over the port selection.</p>
-<p>Systemd and Upstart service files are shipped with the Phoronix Test Suite for those that wish to have the services automatically run as daemons. The only new requirements over the basic Phoronix Test Suite system requirements is having PHP-SQLite support installed and the newer version of PHP or HHVM is recommended for offering the best support.</p>
-<h2>Example Deployments</h2>
-<h3>Use Case A: Unrestricted Internet Access, Local Result Storage</h3>
-<p>Systems on your network with unrestricted Internet access is the easiest and simplest deployment for the Phoronix Test Suite and Phoromatic. After installing the Phoronix Test Suite on the system you wish to designate the Phoromatic Server and have configured the <em>user-config.xml</em> file, simply run:</p>
-<p><strong>$ phoronix-test-suite start-phoromatic-server</strong></p>
-<p>Assuming you have no firewall or permission issues, the built-in web server and WebSocket server should proceed to initiate along with outputting the IP/port information for these services. Unless otherwise disabled from the user configuration file and if avahi-tools is present, the Phoromatic Server will be advertised with Avahi for zero-configuration networking.</p>
-<p>From the Phoromatic web interface you are able to create an account and from there proceed with the creating of test schedules, updating settings, and connecting systems. From the "client systems" you wish to use as the benchmarking nodes, it's simply a matter of running <strong>phoronix-test-suite phoromatic.connect</strong> with zero-conf networking or otherwise follow the information from the Phoromatic web interface for manual setup with the IP/port information.</p>
-<h3>Use Case B: No Internet Available To Client Systems</h3>
-<p>It's possible to run the Phoronix Test Suite and Phoromatic Server without a persistent Internet connection as long as you are able to first download the necessary files to the Phoromatic Server. After installing the Phoronix Test Suite on the system you wish to designate the Phoromatic Server and have configured the <em>user-config.xml</em> file, a few commands from the system while having an Internet connection will be able to cache the needed data:</p>
-<p><strong>$ phoronix-test-suite make-download-cache x264 xonotic ffmpeg</strong></p>
-<p>This command will simply download all of the needed test files for the tests/suites passed to the sub-command. Alternatively you could also pass pts/all to cache all tests. It's important though to just cache the tests/suites you'll be using on your network. This will generate the test file download cache by default to <em>~/.phoronix-test-suite/download-cache/</em> or <em>/usr/share/phoronix-test-suite/download-cache/</em> depending upon your write permissions. You can always run this command later with more test files. Alternatively, if you already have a number of tests installed on the system, simply running "phoronix-test-suite make-download-cache" will generate the cache based upon the currently installed tests.</p>
-<p><strong>$ phoronix-test-suite make-openbenchmarking-cache</strong></p>
-<p>This command will cache as much of the OpenBenchmarking.org meta-data as possible for test profiles and test suites. After the above commands, the Phoromatic Server should no longer need a persistent Internet connection.</p>
-<p><strong>$ phoronix-test-suite start-phoromatic-server</strong></p>
-<p>Proceed to start the Phoromatic Server and operate as normal.</p>
-<p>For the test clients without an Internet connection, as long as they're able to reach the Phoromatic Server, the Phoromatic Server should be able to automatically serve all of the needed test files download cache and OpenBenchmarking.org meta-data to the systems locally.</p>
-<h3>Use Case C: Phoromatic Across The Internet</h3>
-<p>If wishing to use the same Phoromatic Server across multiple geographic locations, it's easily possible -- you just lose out on the zero-conf networking ability. To let the Phoronix Test Suite client systems know about the remote Phoromatic Server, simply add the Phoromatic Server information to the client's <em>PhoromaticServers</em> element within the <em>user-config.xml</em>. Of course, make sure the Phoromatic Server has a globally resolvable IP address and its Phoromatic HTTP/WebSocket ports are open. Once informing the client of the Phoromatic Server, the use cases as above apply in the same manner.</p>
-<h2>Client Setup</h2>
-<p>From Phoronix Test Suite client systems running on the LAN, the following command will report all available detected Phoromatic Servers along with important server and debugging information:</p>
-<p><strong>$ phoronix-test-suite phoromatic.explore</strong></p>
-<p>With the following example output on finding one successful server:</p>
-<p><em>IP: 192.168.1.211<br />
-HTTP PORT: 5447<br />
-WEBSOCKET PORT: 5427<br />
-SERVER: PHP 5.5.9-1ubuntu4.4 Development Server<br />
-PHORONIX TEST SUITE: Phoronix Test Suite v5.4.0m1 [5313]<br />
-DOWNLOAD CACHE: 19 FILES / 2390 MB CACHE SIZE<br />
-SUPPORTED OPENBENCHMARKING.ORG REPOSITORIES:<br />
-      pts - Last Generated: 05 Oct 2014 07:16</em></p>
-<p>Phoromatic Servers are detected by the Phoronix Test Suite through Avahi or if manually configuring the Phoronix Test Suite clients to point to Phoromatic Servers. For networks without Avahi/auto-discovery support or for test systems that may be connecting from another network, the IP address and HTTP port number can be added to the local system's <em>~/.phoronix-test-suite/user-config.xml</em> with the <em>PhoromaticServers</em> element. Adding the <em>IP:port</em> (the Phoromatic Server's HTTP port) to the PhoromaticServers <em>user-config.xml</em> element for will perform targeted probing by the Phoronix Test Suite without any dependence on Avahi. Multiple Phoromatic Servers can be added if each IP:port is delimited by a comma.</p>
-<p>To connect a Phoronix Test Suite system for benchmarking to an account, log into your Phoromatic account from the web-interface and on the main/system pages will be instructions along with a specially formed string to run, e.g. <em>phoronix-test-suite phoromatic.connect 192.168.1.211:5447/I0SSJY</em>. When running that command once on the system(s) to be synced to that account, as the administrator you'll be able to validate/approve the systems from the Phoromatic web interface. After that, whenever the system(s) are to be running benchmarks, simply have the <strong>phoronix-test-suite phoromatic.connect</strong> command running on the system (after the initial account has been synced, simply running <strong>phoronix-test-suite phoromatic.connect</strong> is enough for the system to find the server and its account).</p>
-<h2>Root Administrator</h2>
-<p>The root administrator account is able to manage the server-level settings, e.g. Phoromatic storage location and other global settings related to the Phoronix Test Suite / Phoromatic Server, from the web user-interface.</p>
-<p>To enable the root administrator log-in, first from the server's command-line interface run <strong>phoronix-test-suite phoromatic.set-root-admin-password</strong> to set the password. Following that, you can log into the root administrator account via the web interface via the <em>rootadmin</em> user-name and the set password.</p>
-<h2>Other Advice</h2>
-<h3>Disable Internet Precaution</h3>
-<p>If you have an Internet connection but want to ensure your Phoronix Test Suite client doesn't attempt to use it for any matter, via the <em>~/.phoronix-test-suite/user-config.xml</em> you can set <em>NoInternetCommunication</em> to <em>TRUE</em>. There's also a NoNetworkCommunication tag, but setting that to TRUE will disable any form of network communication -- including communication with the Phoromatic Server.</p>
-<h3>Ports / Services</h3>
-<p>The Phoromatic Server process currently relies upon a PHP/HHVM built-in web server process and a PTS-hosted WebSocket server. The web server process handles the web UI and much of the responsibilities of the Phoromatic Server. Over time the PTS WebSocket server will be increasingly utilized for bi-directional, real-time communication between the server and clients -- including for features like viewing real-time hardware sensors of client systems from the server UI.</p>
-<h3>Systemd / Upstart</h3>
-<p>Packaged with the Phoronix Test Suite are basic <em>phoromatic-client</em> and <em>phoromatic-server</em> configurations for both Upstart and systemd init systems. The <em>phoromatic-server</em> configuration will launch the Phoronix Test Suite's Phoromatic Server and the <em>phoromatic-client</em> service will attempt to connect to a <u>pre-configured</u> Phoromatic Server. The systemd service files will automatically be installed via the Phoronix Test Suite <em>install-sh</em> process while the Upstart jobs can be copied from <em>deploy/phoromatic-upstart/*</em> to <em>/etc/init</em>.</p>
-<h3>Cache Verification</h3>
-<p>To confirm the files accessible to Phoronix Test Suite client systems, from the Phoromatic Server web user-interface go to the <em>settings</em> page followed by the <em>cache settings</em> link to view information about the download and OpenBenchmarking.org caches. From the client systems, running <strong>phoronix-test-suite phoromatic.explore</strong> will also supply cache statistics.</p>
-<h3>Log Files</h3>
-<p>The Phoromatic Server will produce a log file of events / debugging information to <em>~/.phoronix-test-suite/phoromatic.log</em> or <em>/var/log/phoromatic.log</em> depending upon the service's permissions. When running the Phoronix Test Suite Phoromatic client, the log will be written to one of the respective locations in <em>phoronix-test-suite.log</em>.</p>
-<h3>Multi-User Accounts</h3>
-<p>For each time a user account is made from the Phoromatic web UI's log-in page, all of the test schedules, systems, and other account information is separate to allow for a completely isolated multi-user system. If a main administrator (the one creating the account) wishes to have multiple users sharing the same account data, that user can create additional accounts from the <em>Users</em> tab of their account. The main administrator can make an additional administrator account or a &quot;viewer&quot; account that can consume the account's data but not create/modify the schedules, systems, or other account details.</p>
-<h3>
-<h3>File Locations</h3>
-<p>When running the Phoronix Test Suite Phoromatic Server as root, rather than using the <em>~/.phoronix-test-suite/</em> directory, the standard Linux file-system hierarchy standard is honored. The main storage path is <em>/var/lib/phoronix-test-suite/</em>, the user configuration file is <em>/etc/phoronix-test-suite.xml</em>, and <em>/var/cache/phoronix-test-suite/</em> for cache files.</p>
-<h3>Uploading Other Test Results</h3>
-<p>Unscheduled test results and other results found on connected systems to a Phoromatic account can upload the data to the Phoromatic Server using the <em>phoronix-test-suite phoromatic.upload-result &lt;result file identifier &gt;</em> sub-command.</p>
-<h3>User Context File Logging</h3>
-<p>For those utilizing custom set context script files as part of the Phoromatic test schedule, any important notes / log information can be written to the file specified by the <em>PHOROMATIC_LOG_FILE</em> environment variable set while running the user context scripts. The contents of that file is then sent to the Phoromatic Server otherwise the standard output of the script's execution is submitted to the Phoromatic Server for logging. These logs can then be viewed by the Phoromatic Server along with the test results. Other environment variables accessible when running a user context script include <em>PHOROMATIC_TRIGGER</em>, <em>PHOROMATIC_SCHEDULE_ID</em>, and <em>PHOROMATIC_SCHEDULE_PROCESS</em>.</p>
-</body>
-</html>

documentation/phoromatic.md

@@ -1,139 +0,0 @@
-
-# Phoronix Test Suite Phoromatic
-
-## Phoromatic Server
-
-### Introduction
-Phoromatic is a remote management system for the Phoronix Test Suite. Phoromatic allows the automatic (hence the name *Phoro-matic* ) scheduling of tests, remote installation of new tests, and the management of multiple test systems all through an intuitive, easy-to-use web interface. Tests can be scheduled to automatically run on a routine basis across multiple test systems. The test results are then available from this central, secure location.
-
-Phoromatic was originally introduced with Phoronix Test Suite 2.0 via Phoromatic.com as a project going back to 2008~2009. Phoromatic.com debuted as a hosted instance with the option of behind-the-firewall licensing for use within organizations. With Phoronix Test Suite 5.2 the model shifted to offer a local, open-source version of Phoromatic built into the Phoronix Test Suite code-base. Thanks to continued enterprise development, with Phoronix Test Suite 5.4 is now a fully-functioning, built-in version of Phoromatic that's open-source and can be used for behind-the-firewall testing without needing to push results to OpenBenchmarking.org and the ability to keep all results private.
-
-Phoromatic in Phoronix Test Suite 5.4 also has the ability to support zero-conf  network discovery using Avahi and the automatic distribution of needed test profiles/suites and test files. Phoronix Test Suite 5.4's Phoromatic is a significant breakthrough for open-source testing particularly those running this GPL benchmarking software within test labs and other large organizations.
-
-
-### Features
-Built atop the Phoronix Test Suite, Phoromatic offers many features for both enterprise and community/personal users:
-
-#### Automated Scheduling
-Whether it is every evening at 6:00PM, once every Thursday at 10:00AM or somewhere in between, Phoromatic can schedule tests to be run at user-defined intervals. The testing schedules can be updated through Phoromatic web interface. After the test(s) have run, the results will be immediately uploaded to Phoromatic.
-
-#### Extensible
-Any test profile or test suite that is compliant with the Phoronix Test Suite specification will work with Phoromatic. Phoromatic is able to leverage the hundreds of test profiles and test suites currently in the Phoronix Test Suite via OpenBenchmarking.org, along with any custom or proprietary test profiles you or your company utilize. Additionally, the Phoromatic interface allows the user to construct their own test suite(s).
-
-#### Remote Testing
-Once the test system is setup, all testing and management of that system can be done remotely. There is no need to execute Phoronix Test Suite commands locally using the GUI or command line version, but instead nearly all of the same features are accessible from the Phoromatic interface.
-
-#### Multi-System Support
-A single Phoromatic account is able to manage multiple test systems running the Phoronix Test Suite. Phoromatic supports grouping together test systems, tagging, and other features to support effectively managing many test systems. From the Phoromatic interface, installed system hardware and software from a given system can also be viewed.
-
-#### Turn-Key Deployment
-No additional software needs to be installed to support Phoromatic; all that's needed is Phoronix Test Suite 5.4 or later for full compatibility. New test systems can easily be synced with a given Phoromatic account by running a single command from the Phoronix Test Suite client.
-
-#### Result Management
-Test results are automatically uploaded to the Phoromatic account and remain private unless you opt to upload them to OpenBenchmarking.org. From the Phoromatic interface, results from multiple test systems can easily be compared and multiple results from the same systems can be used to track performance over time. There are also options to look at the statistical significance of the results and other features to efficiently and effectively analyze the system's performance.
-
-#### Decentralized
-Once the Phoronix Test Suite running on the Phoromatic Server has been able to cache all of the OpenBenchmarking.org test files and the needed files for each test, Phoromatic with any Phoronix Test Suite clients on your LAN can run fully decentralized without the need for a constant stream of OpenBenchmarking.org communication or Internet connection for that matter. (The only exception would be if your local systems don't have all their needed external dependencies and your system's package manager would need to install components like a compiler or necessary system libraries.
-
-#### Fully Open-Source
-Phoromatic is now fully open-source within the Phoronix Test Suite code-base for fostering greater development and new capabilities. Patches are welcome and Phoronix Media is available to provide commercial support and custom engineering services around Phoromatic and the Phoronix Test Suite.
-
-
-### Phoromatic Server Setup
-Phoromatic is built into the Phoronix Test Suite code-base and should be found in all packaged versions of the **phoronix-test-suite** . Starting the Phoromatic Server entails running phoronix-test-suite start-phoromatic-server after configuring the server information within *~/.phoronix-test-suite/user-config.xml* . The Phoromatic Server can with or without root permissions depending upon your firewall and the port numbers you wish to use for the server.
-
-On the "client side", any up-to-date version of the Phoronix Test Suite can automatically communicate with the Phoromatic Server. If Avahi support is available (commonly in Linux distribution repositories as _avahi-tools_ ), there should be zero-conf discovery if the Phoromatic Server and client systems are on the same LAN. If a Phoronix Test Suite client discovers a Phoromatic Server, it will attempt to use it automatically as a local download cache. In the event of no Internet connection, it will also attempt to obtain the needed OpenBenchmarking.org test/suite meta-data from the Phoromatic Server based upon its archived meta-data. This allows the Phoronix Test Suite / Phoromatic deployment on the LAN to be self-sustaining without an Internet connection as long as the systems have all installed test dependencies.
-
-Further configuration of the setup parameters for the Phoromatic Server and Phoronix Test Suite clients can be tuned via the *~/.phoronix-test-suite/user-config.xml* file. All control and configuration of the Phoromatic Server is done via the web-based interface when the Phoromatic Server is active.
-
-The Phoromatic Server utilizes PHP/HHVM's built-in web-server capabilities and there's also a Phoronix Test Suite built-in WebSocket server that's also initiated for back-end processing. At this time there are no ports set by default for these services but must be defined within the user configuration file. With the Avahi zero-conf network discovery and other automated detection in place, there's little restrictions over the port selection.
-
-Systemd and Upstart service files are shipped with the Phoronix Test Suite for those that wish to have the services automatically run as daemons. The only new requirements over the basic Phoronix Test Suite system requirements is having PHP-SQLite support installed and the newer version of PHP or HHVM is recommended for offering the best support.
-
-
-### Example Deployments
-#### Use Case A: Unrestricted Internet Access, Local Result Storage
-Systems on your network with unrestricted Internet access is the easiest and simplest deployment for the Phoronix Test Suite and Phoromatic. After installing the Phoronix Test Suite on the system you wish to designate the Phoromatic Server and have configured the *user-config.xml* file, simply run:
-
-**$ phoronix-test-suite start-phoromatic-server**
-
-Assuming you have no firewall or permission issues, the built-in web server and WebSocket server should proceed to initiate along with outputting the IP/port information for these services. Unless otherwise disabled from the user configuration file and if avahi-tools is present, the Phoromatic Server will be advertised with Avahi for zero-configuration networking.
-
-From the Phoromatic web interface you are able to create an account and from there proceed with the creating of test schedules, updating settings, and connecting systems. From the "client systems" you wish to use as the benchmarking nodes, it's simply a matter of running **phoronix-test-suite phoromatic.connect** with zero-conf networking or otherwise follow the information from the Phoromatic web interface for manual setup with the IP/port information.
-
-#### Use Case B: No Internet Available To Client Systems
-It's possible to run the Phoronix Test Suite and Phoromatic Server without a persistent Internet connection as long as you are able to first download the necessary files to the Phoromatic Server. After installing the Phoronix Test Suite on the system you wish to designate the Phoromatic Server and have configured the *user-config.xml* file, a few commands from the system while having an Internet connection will be able to cache the needed data:
-
-**$ phoronix-test-suite make-download-cache x264 xonotic ffmpeg**
-
-This command will simply download all of the needed test files for the tests/suites passed to the sub-command. Alternatively you could also pass pts/all to cache all tests. It's important though to just cache the tests/suites you'll be using on your network. This will generate the test file download cache by default to *~/.phoronix-test-suite/download-cache/* or */usr/share/phoronix-test-suite/download-cache/* depending upon your write permissions. You can always run this command later with more test files. Alternatively, if you already have a number of tests installed on the system, simply running "phoronix-test-suite make-download-cache" will generate the cache based upon the currently installed tests.
-
-**$ phoronix-test-suite make-openbenchmarking-cache**
-
-This command will cache as much of the OpenBenchmarking.org meta-data as possible for test profiles and test suites. After the above commands, the Phoromatic Server should no longer need a persistent Internet connection.
-
-**$ phoronix-test-suite start-phoromatic-server**
-
-Proceed to start the Phoromatic Server and operate as normal.
-
-For the test clients without an Internet connection, as long as they're able to reach the Phoromatic Server, the Phoromatic Server should be able to automatically serve all of the needed test files download cache and OpenBenchmarking.org meta-data to the systems locally.
-
-#### Use Case C: Phoromatic Across The Internet
-If wishing to use the same Phoromatic Server across multiple geographic locations, it's easily possible -- you just lose out on the zero-conf networking ability. To let the Phoronix Test Suite client systems know about the remote Phoromatic Server, simply add the Phoromatic Server information to the client's *PhoromaticServers* element within the *user-config.xml* . Of course, make sure the Phoromatic Server has a globally resolvable IP address and its Phoromatic HTTP/WebSocket ports are open. Once informing the client of the Phoromatic Server, the use cases as above apply in the same manner.
-
-
-### Client Setup
-From Phoronix Test Suite client systems running on the LAN, the following command will report all available detected Phoromatic Servers along with important server and debugging information:
-
-**$ phoronix-test-suite phoromatic.explore**
-
-With the following example output on finding one successful server:
-
-*IP: 192.168.1.211
-HTTP PORT: 5447
-WEBSOCKET PORT: 5427
-SERVER: PHP 5.5.9-1ubuntu4.4 Development Server
-PHORONIX TEST SUITE: Phoronix Test Suite v5.4.0m1 [5313]
-DOWNLOAD CACHE: 19 FILES / 2390 MB CACHE SIZE
-SUPPORTED OPENBENCHMARKING.ORG REPOSITORIES:
-      pts - Last Generated: 05 Oct 2014 07:16*
-
-Phoromatic Servers are detected by the Phoronix Test Suite through Avahi or if manually configuring the Phoronix Test Suite clients to point to Phoromatic Servers. For networks without Avahi/auto-discovery support or for test systems that may be connecting from another network, the IP address and HTTP port number can be added to the local system's *~/.phoronix-test-suite/user-config.xml* with the *PhoromaticServers* element. Adding the *IP:port* (the Phoromatic Server's HTTP port) to the PhoromaticServers *user-config.xml* element for will perform targeted probing by the Phoronix Test Suite without any dependence on Avahi. Multiple Phoromatic Servers can be added if each IP:port is delimited by a comma.
-
-To connect a Phoronix Test Suite system for benchmarking to an account, log into your Phoromatic account from the web-interface and on the main/system pages will be instructions along with a specially formed string to run, e.g. *phoronix-test-suite phoromatic.connect 192.168.1.211:5447/I0SSJY* . When running that command once on the system(s) to be synced to that account, as the administrator you'll be able to validate/approve the systems from the Phoromatic web interface. After that, whenever the system(s) are to be running benchmarks, simply have the **phoronix-test-suite phoromatic.connect** command running on the system (after the initial account has been synced, simply running **phoronix-test-suite phoromatic.connect** is enough for the system to find the server and its account).
-
-
-### Root Administrator
-The root administrator account is able to manage the server-level settings, e.g. Phoromatic storage location and other global settings related to the Phoronix Test Suite / Phoromatic Server, from the web user-interface.
-
-To enable the root administrator log-in, first from the server's command-line interface run **phoronix-test-suite phoromatic.set-root-admin-password** to set the password. Following that, you can log into the root administrator account via the web interface via the *rootadmin* user-name and the set password.
-
-
-### Other Advice
-#### Disable Internet Precaution
-If you have an Internet connection but want to ensure your Phoronix Test Suite client doesn't attempt to use it for any matter, via the *~/.phoronix-test-suite/user-config.xml* you can set *NoInternetCommunication* to *TRUE* . There's also a NoNetworkCommunication tag, but setting that to TRUE will disable any form of network communication -- including communication with the Phoromatic Server.
-
-#### Ports / Services
-The Phoromatic Server process currently relies upon a PHP/HHVM built-in web server process and a PTS-hosted WebSocket server. The web server process handles the web UI and much of the responsibilities of the Phoromatic Server. Over time the PTS WebSocket server will be increasingly utilized for bi-directional, real-time communication between the server and clients -- including for features like viewing real-time hardware sensors of client systems from the server UI.
-
-#### Systemd / Upstart
-Packaged with the Phoronix Test Suite are basic *phoromatic-client* and *phoromatic-server* configurations for both Upstart and systemd init systems. The *phoromatic-server* configuration will launch the Phoronix Test Suite's Phoromatic Server and the *phoromatic-client* service will attempt to connect to a _pre-configured_ Phoromatic Server. The systemd service files will automatically be installed via the Phoronix Test Suite *install-sh* process while the Upstart jobs can be copied from *deploy/phoromatic-upstart/** to */etc/init* .
-
-#### Cache Verification
-To confirm the files accessible to Phoronix Test Suite client systems, from the Phoromatic Server web user-interface go to the *settings* page followed by the *cache settings* link to view information about the download and OpenBenchmarking.org caches. From the client systems, running **phoronix-test-suite phoromatic.explore** will also supply cache statistics.
-
-#### Log Files
-The Phoromatic Server will produce a log file of events / debugging information to *~/.phoronix-test-suite/phoromatic.log* or */var/log/phoromatic.log* depending upon the service's permissions. When running the Phoronix Test Suite Phoromatic client, the log will be written to one of the respective locations in *phoronix-test-suite.log* .
-
-#### Multi-User Accounts
-For each time a user account is made from the Phoromatic web UI's log-in page, all of the test schedules, systems, and other account information is separate to allow for a completely isolated multi-user system. If a main administrator (the one creating the account) wishes to have multiple users sharing the same account data, that user can create additional accounts from the *Users* tab of their account. The main administrator can make an additional administrator account or a "viewer" account that can consume the account's data but not create/modify the schedules, systems, or other account details.
-
-#### File Locations
-When running the Phoronix Test Suite Phoromatic Server as root, rather than using the *~/.phoronix-test-suite/* directory, the standard Linux file-system hierarchy standard is honored. The main storage path is */var/lib/phoronix-test-suite/* , the user configuration file is */etc/phoronix-test-suite.xml* , and */var/cache/phoronix-test-suite/* for cache files.
-
-#### Uploading Other Test Results
-Unscheduled test results and other results found on connected systems to a Phoromatic account can upload the data to the Phoromatic Server using the *phoronix-test-suite phoromatic.upload-result <result file identifier >* sub-command.
-
-#### User Context File Logging
-For those utilizing custom set context script files as part of the Phoromatic test schedule, any important notes / log information can be written to the file specified by the *PHOROMATIC_LOG_FILE* environment variable set while running the user context scripts. The contents of that file is then sent to the Phoromatic Server otherwise the standard output of the script's execution is submitted to the Phoromatic Server for logging. These logs can then be viewed by the Phoromatic Server along with the test results. Other environment variables accessible when running a user context script include *PHOROMATIC_TRIGGER* , *PHOROMATIC_SCHEDULE_ID* , and *PHOROMATIC_SCHEDULE_PROCESS* .
-

documentation/phoronix-test-suite-window.md

@@ -1,40 +0,0 @@
-
-# Phoronix Test Suite On Windows
-
-### Introduction
-Phoronix Test Suite 8.0 features rewritten Windows support that is at a near feature parity to the program's long-standing support for Linux, macOS, BSD and Solaris operating systems. To make it abundantly clear, if you are using a Phoronix Test Suite version pre-8.0, you are best upgrading or ideally using Phoronix Test Suite Git as the Windows support remains in very active development at the moment as of early 2018.
-
-The Phoronix Test Suite Windows support currently targets **Windows 10 x64** and **Windows Server 2016 x64** . Earlier versions of Windows, namely Windows Server 2012 and Windows 8, may work to some extent but some hardware/software reporting features and other capabilities may be missing or report warning messages. The Phoronix Test Suite Windows support is also exclusively focused on x86 64-bit support: the Phoronix Test Suite itself will run on x86 32-bit but many of the program dependencies are configured for making use of 64-bit binaries.
-
-
-### Windows Setup / Dependencies
-As with Phoronix Test Suite on Linux and other operating systems, the principal dependency is on PHP (PHP v5.3 or newer, including PHP 7.x). Running the *phoronix-test-suite.bat* file launcher for the Phoronix Test Suite on Windows will attempt to download and setup PHP on the system under *C:\PHP* as the default location should PHP support not be found within your system's *Program Files* directories. The PHP Windows build does depend upon Microsoft Visual C++ redistributable libraries, which the Windows launcher will also attempt to download and install if needed.
-
-The Phoronix Test Suite on Windows does depend upon [Cygwin](https://www.cygwin.com/) for its Bash interpreter and other basic utilities to ease the process of porting test profiles to Windows with being able to use many of the same test installation scripts on Windows/Linux/macOS/BSD/Solaris then largely unmodified. Most of the Windows tests depend upon their respective native Windows applications/binaries while this Cygwin support is a convenience for handling these Bash setup scripts and also some test profiles that depend upon a GNU toolchain. The Phoronix Test Suite will attempt to download and setup Cygwin on the system if Cygwin isn't found in its default location of *C:\cygwin64* .
-
-Various test profiles may depend upon other "external dependencies" like Python, PERL, Steam, and Java, as examples. The Phoronix Test Suite as with its support for other operating systems and Linux distributions will attempt to install these needed dependencies on a per-test basis when needed if existing support is not detected on the system.
-
-
-### Running The Phoronix Test Suite On Windows
-The Phoronix Test Suite can run from its local directory and does not need to be "installed" to a system path or any other "setup" process prior to execution. On a clean install of Windows 10 x64 or Windows Server 2016, deploying the Phoronix Test Suite is designed to be as easy and straight-forward as possible:
-
-1. Download the Phoronix Test Suite 8.0+ or [Phoronix-Test-Suite from GitHub](https://github.com/phoronix-test-suite/phoronix-test-suite) ( [zip file](https://github.com/phoronix-test-suite/phoronix-test-suite/archive/master.zip) ).
-
-2. From the Command Prompt or PowerShell, enter the *phoronix-test-suite* directory whether it be from Git or a zipped download.
-
-3. Run the *phoronix-test-suite.bat* file that should proceed to run the Phoronix Test Suite just as you would on any other operating system. If needed the Phoronix Test Suite will try to initially download and setup PHP if needed followed by the attempted automatic Cygwin setup, etc.
-
-4. Any of the Phoronix Test Suite commands from other operating systems should work on Windows. If you are new to the Phoronix Test Suite, you may enjoy a bit more guided experience by running the **phoronix-test-suite shell** command.
-
-
-### Test Profiles On Windows
-As of March 2018, around 50 of the test profiles are currently compatible with the Phoronix Test Suite on Windows. This includes many of the popular benchmarks and other interesting test cases. Over time more test profiles will continue to be ported to Windows where applicable and there are also some Windows-only tests also supported for execution by the Phoronix Test Suite.
-
-
-### Getting Started
-Besides **phoronix-test-suite shell** and **phoronix-test-suite help** , there is also **phoronix-test-suite interactive** for helping new users understand Phoronix Test Suite benchmarking. Long story short, it should be as easy as running **phoronix-test-suite benchmark c-ray** or **phoronix-test-suite benchmark crafty** as some examples for carrying out automated, cross-platform benchmarks in a side-by-side and fully-reproducible manner.
-
-
-### Support
-Community technical support is available via [GitHub](https://github.com/phoronix-test-suite/phoronix-test-suite/issues) or general inquiries via [the Phoronix Forums](https://www.phoronix.com/forums/forum/phoronix/phoronix-test-suite) . For enterprise inquiries, commercial support, and custom engineering services, [contact us](http://phoronix-test-suite.com/?k=commercial) .
-

documentation/phoronix-test-suite.html

@@ -209,7 +209,7 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 		<h1>Phoronix Test Suite</h1>
 		</div>
 		<div id="pts_banner_nav"></div>
-		<div id="pts_template_body"><ol><li><a href="#GettingStarted">Getting Started</a></li><li><a href="#UserOptions">User Options</a></li><li><a href="#ModuleOptions">Module Options</a></li><li><a href="#InstallationInstructions">Installation Instructions</a></li><li><a href="#ExternalDependencies">External Dependencies</a></li><li><a href="#Configuration">Configuration</a></li><li><a href="#GeneralInformation">General Information</a></li><li><a href="#VirtualTestSuites">Virtual Test Suites</a></li><li><a href="#ComponentTesting">Component Testing</a></li><li><a href="#Phoromatic">Phoromatic</a></li><li><a href="#OfflineImprovements+ConfidentialTesting/AvoidingAccidentalResultUploads">Offline Improvements + Confidential Testing / Avoiding Accidental Result Uploads</a></li><li><a href="#DevelopmentCredits">Development Credits</a></li></ol><hr style="height: 50px; border: 0;"><a name="GettingStarted"></a><h1>Getting Started</h1>
+		<div id="pts_template_body"><ol><li><a href="#GettingStarted">Getting Started</a></li><li><a href="#UserOptions">User Options</a></li><li><a href="#ModuleOptions">Module Options</a></li><li><a href="#InstallationInstructions">Installation Instructions</a></li><li><a href="#PhoronixTestSuiteOnWindows">Phoronix Test Suite On Windows</a></li><li><a href="#ExternalDependencies">External Dependencies</a></li><li><a href="#Configuration">Configuration</a></li><li><a href="#GeneralInformation">General Information</a></li><li><a href="#VirtualTestSuites">Virtual Test Suites</a></li><li><a href="#ComponentTesting">Component Testing</a></li><li><a href="#PhoronixTestSuitePhoromatic">Phoronix Test Suite Phoromatic</a></li><li><a href="#OfflineImprovements+ConfidentialTesting/AvoidingAccidentalResultUploads">Offline Improvements + Confidential Testing / Avoiding Accidental Result Uploads</a></li><li><a href="#DevelopmentCredits">Development Credits</a></li></ol><hr style="height: 50px; border: 0;"><a name="GettingStarted"></a><h1>Getting Started</h1>
 <h1>Overview</h1>
 <p>The Phoronix Test Suite is the most comprehensive testing and benchmarking platform available for Linux, Solaris, macOS, Windows, and BSD operating systems. The Phoronix Test Suite allows for carrying out tests in a fully automated manner from test installation to execution and reporting. All tests are meant to be easily reproducible, easy-to-use, and support fully automated execution. The Phoronix Test Suite is open-source under the GNU GPLv3 license and is developed by Phoronix Media in cooperation with partners. Version 1.0 of the Phoronix Test Suite was publicly released in 2008.</p>
 <p>The Phoronix Test Suite client itself is a test framework for providing seamless execution of test profiles and test suites. There are more than 400 tests available by default, which are transparently available via <a href="http://openbenchmarking.org/">OpenBenchmarking.org</a> integration. Of these default test profiles there is a range of sub-systems that can be tested and a range of hardware from mobile devices to desktops and worksrtations/servers. New tests can be easily introduced via the Phoronix Test Suite's extensible test architecture, with test profiles consisting of XML files and shell scripts. Test profiles can produce a quantitative result or other qualitative/abstract results like image quality comparisons and pass/fail. Using Phoronix Test Suite modules, other data can also be automatically collected at run-time such as the system power consumption, disk usage, and other software/hardware sensors. Test suites contain references to test profiles to execute as part of a set or can also reference other test suites. Test suites are defined via an XML schema.</p>
@@ -239,6 +239,9 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 <h3>system-info<em>  </em>
 </h3>
 <p>Display the installed system hardware and software information as detected by the Phoronix Test Suite Phodevi Library.</p>
+<h3>system-properties<em>  </em>
+</h3>
+<p>Display various hardware/software system properties detected by the Phoronix Device Interface (Phodevi) library.</p>
 <h3>system-sensors<em>  </em>
 </h3>
 <p>Display the installed system hardware and software sensors in real-time as detected by the Phoronix Test Suite Phodevi Library.</p>
@@ -262,6 +265,9 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 <h3>benchmark<em>  [Test | Suite | OpenBenchmarking ID | Test Result]  ...</em>
 </h3>
 <p>This option will install the selected test(s) (if needed) and will proceed to run the test(s). This option is equivalent to running phoronix-test-suite with the install option followed by the run option. Multiple arguments can be supplied to run additional tests at the same time and save the results into one file.</p>
+<h3>estimate-install-time<em>  [Test | Suite | OpenBenchmarking ID | Test Result]</em>
+</h3>
+<p>This option will provide estimates for test install/setup time length.</p>
 <h3>estimate-run-time<em>  [Test | Suite | OpenBenchmarking ID | Test Result]</em>
 </h3>
 <p>This option will provide estimates for test run-time / length.</p>
@@ -321,6 +327,9 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 <h3>clone-result<em>  [OpenBenchmarking ID]  ...</em>
 </h3>
 <p>This option will download a local copy of a file that was saved to OpenBenchmarking.org, as long as a valid public ID is supplied.</p>
+<h3>enable-repo<em>  </em>
+</h3>
+<p>This option is used if wanting to add a new OpenBenchmarking.org account/repository to your system for enabling third-party/unofficial test profiles and test suites.</p>
 <h3>list-recommended-tests<em>  </em>
 </h3>
 <p>This option will list recommended test profiles for benchmarking sorted by hardware sub-system. The recommended tests are determined via querying OpenBenchmarking.org and determining the most popular tests for a given environment based upon the number of times a test profile has been downloaded, the number of test results available on OpenBenchmarking.org for a given test profile, the age of the test profile, and other weighted factors.</p>
@@ -355,6 +364,9 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 </h3>
 <p>This option can be used for uploading a test suite to your account on OpenBenchmarking.org. By uploading your test suite to OpenBenchmarking.org, others are then able to browse and access this test suite for easy distribution.</p>
 <h1>Information</h1>
+<h3>check-tests<em>  [Test]</em>
+</h3>
+<p>This option will perform a check on one or more test profiles to determine if there have been any vendor changes to the filename, filesize, url location, md5 and sha256 checksums.</p>
 <h3>info<em>  [Test | Suite | OpenBenchmarking ID | Test Result]</em>
 </h3>
 <p>This option will show details about the supplied test, suite, virtual suite, or result file.</p>
@@ -406,6 +418,9 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 <h3>search<em>  </em>
 </h3>
 <p>This option provides command-line searching abilities for test profiles / test suites / test results. The search query can be passed as a parameter otherwise the user is prompted to input their search query..</p>
+<h3>test-to-suite-map<em>  </em>
+</h3>
+<p>This option will list all test profiles and any test suites each test belongs to.</p>
 <h1>Asset Creation</h1>
 <h3>build-suite<em>  </em>
 </h3>
@@ -431,6 +446,9 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 <h3>inspect-test-profile<em>  [Test]</em>
 </h3>
 <p>This option can be used for inspecting a Phoronix Test Suite test profile with providing inside details on test profiles for debugging / evaluation / learning purposes.</p>
+<h3>rebuild-test-suite<em>  [Suite]</em>
+</h3>
+<p>This option will regenerate the local test suite XML file against the OpenBenchmarking.org specification. This can be used to clean up any existing XML syntax / styling issues, etc.</p>
 <h3>result-file-to-suite<em>  [Test Result]</em>
 </h3>
 <p>This option will guide the user through the process of generating their own test suite, which they can then run, that is based upon an existing test results file.</p>
@@ -462,12 +480,12 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 <h3>extract-from-result-file<em>  [Test Result]</em>
 </h3>
 <p>This option will extract a single set of test results from a saved results file that contains multiple test results that have been merged. The user is the prompted to specify a new result file name and select which result identifier to extract.</p>
+<h3>keep-results-in-result-file<em>  [Test Result]</em>
+</h3>
+<p>This option is the inverse of the remove-results-from-result-file sub-command. If you wish to remove all results but those listed from a given result file, this option can be used. The user must specify a saved results file and then they will be prompted to provide a string to search for in keeping those results in that given result file but removing all other data.</p>
 <h3>merge-results<em>  [Test Result]  ...</em>
 </h3>
 <p>This option will manually merge multiple sets of test results generated by the Phoronix Test Suite.</p>
-<h3>refresh-graphs<em>  [Test Result]</em>
-</h3>
-<p>This option will re-render and save all result graphs within a saved file. This option can be used when making modifications to the graphing code or its color/option configuration file and testing the changes.</p>
 <h3>remove-result<em>  [Test Result]</em>
 </h3>
 <p>This option will permanently remove the saved file set that is set as the first argument.</p>
@@ -507,6 +525,9 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 <h3>show-result<em>  [Test Result]</em>
 </h3>
 <p>Open up the test results in the Phoronix Test Suite Result Viewer or on OpenBenchmarking.org.</p>
+<h3>workload-topology<em>  [Test Result]</em>
+</h3>
+<p>This option will read a saved test results file and print the test profiles contained within and their arrangement within different test suites for getting an idea as to the workload topology/make-up / logical groupings of the benchmarks being run.</p>
 <h1>Other</h1>
 <h3>commands<em>  </em>
 </h3>
@@ -526,22 +547,6 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 <h3>version<em>  </em>
 </h3>
 <p>This option will display the Phoronix Test Suite client version.</p>
-<h1>Result Analysis</h1>
-<h3>analyze-all-runs<em>  [Test Result]</em>
-</h3>
-<p>This option will generate a candlestick graph showing the distribution of results from all trial runs. The candlestick graph is similar to the Japanese candlestick charts used by the financial industry, except instead of representing stock data it is numerical result data from all trial runs.\n\nThe tip of the upper-wick represents the highest value of the test runs with the tip of the lower-wick representing the lowest value of all test runs. The upper-edge of the candle body represents the first or last run value and the lower-edge represents the first or last run value. Lastly, if the last run value is less than the first run value, the candle body is the same color as the graph background, otherwise the last run value is greater.</p>
-<h3>executive-summary<em>  [Test Result]</em>
-</h3>
-<p>This option will attempt to auto-generate a textual executive summary for a result file to highlight prominent results / averages.</p>
-<h3>result-file-confidence<em>  [Test Result]</em>
-</h3>
-<p>This option will read a saved test results file and display various statistics on the confidence of the results with the standard deviation, three-sigma values, and other metrics while color-coding "passing" results in green.</p>
-<h3>result-file-stats<em>  [Test Result]</em>
-</h3>
-<p>This option is used if you wish to analyze a result file by seeing various statistics on the result data for result files containing at least two sets of data.</p>
-<h3>wins-and-losses<em>  [Test Result]</em>
-</h3>
-<p>This option is used if you wish to analyze a result file to see which runs produced the most wins/losses of those result identifiers in the saved file.</p>
 <h1>Modules</h1>
 <h3>auto-load-module<em>  </em>
 </h3>
@@ -577,6 +582,19 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 <h3>user-config-set<em>  </em>
 </h3>
 <p>This option can be used for setting an XML value in the Phoronix Test Suite user configuration file.</p>
+<h1>Result Analysis</h1>
+<h3>executive-summary<em>  [Test Result]</em>
+</h3>
+<p>This option will attempt to auto-generate a textual executive summary for a result file to highlight prominent results / averages.</p>
+<h3>result-file-confidence<em>  [Test Result]</em>
+</h3>
+<p>This option will read a saved test results file and display various statistics on the confidence of the results with the standard deviation, three-sigma values, and other metrics while color-coding "passing" results in green.</p>
+<h3>result-file-stats<em>  [Test Result]</em>
+</h3>
+<p>This option is used if you wish to analyze a result file by seeing various statistics on the result data for result files containing at least two sets of data.</p>
+<h3>wins-and-losses<em>  [Test Result]</em>
+</h3>
+<p>This option is used if you wish to analyze a result file to see which runs produced the most wins/losses of those result identifiers in the saved file.</p>
 <h1>Phoromatic</h1>
 <h3>start-phoromatic-server<em>  </em>
 </h3>
@@ -598,6 +616,9 @@ along with this program. If not, see <http://www.gnu.org/licenses/>.
 <h2>Generate Perf FlameGraphs For Tests</h2>
 <p>Setting FLAME_GRAPH_PATH=&lt;path to flamegraph path&gt; will auto-load and enable this Phoronix Test Suite module. The module will generate a Linux perf FlameGraph for each test run during the benchmarking process. Details on FlameGraph @ https://github.com/brendangregg/FlameGraph</p>
 <p>This module utilizes the following environmental variables: FLAME_GRAPH_PATH.</p>
+<h2>Flush Caches</h2>
+<p>Loading this module will ensure caches (page cache, swap, etc) automatically get flushed prior to running any test.</p>
+<p>This module utilizes the following environmental variables: PTS_FLUSH_CACHES.</p>
 <h2>Graphics Override</h2>
 <p>This module allows you to override some graphics rendering settings for the ATI and NVIDIA drivers while running the Phoronix Test Suite.</p>
 <p>This module utilizes the following environmental variables: FORCE_AA, FORCE_AF.</p>
@@ -707,24 +728,19 @@ Supported Options:
   - all.hdd
   - hdd.read-speed
   - all.hdd.read-speed
-  - hdd.read-speed.sda
-  - hdd.read-speed.sdb
   - hdd.read-speed.nvme0n1
+  - hdd.read-speed.mmcblk0
   - hdd.temp
   - all.hdd.temp
-  - hdd.temp.sda
-  - hdd.temp.sdb
   - hdd.temp.nvme0n1
+  - hdd.temp.mmcblk0
   - hdd.write-speed
   - all.hdd.write-speed
-  - hdd.write-speed.sda
-  - hdd.write-speed.sdb
   - hdd.write-speed.nvme0n1
+  - hdd.write-speed.mmcblk0
   - all.memory
   - memory.temp
   - memory.usage
-  - all.network
-  - network.usage
   - all.swap
   - swap.usage
   - all.sys
@@ -736,12 +752,18 @@ Supported Options:
   - all.sys.voltage
 
 NOTE: Use the "system-sensors" command to see what sensors are available for monitoring on the system.</p>
+<h2>Test Timeout</h2>
+<p>This module allows killing a test if it exceeds a defined threshold, such as if the test is hung, etc. TEST_TIMEOUT_AFTER= environment variable can be used for controlling the behavior. When this variable is set, the value will can be set to "auto" or a positive integer. The value indicates the number of minutes until a test run should be aborted, such as for a safeguard against hung/deadlocked processes or other issues. Setting this to a high number as a backup would be recommended for fending off possible hangs / stalls in the testing process if the test does not quit on its own for whatever reason. If the value is "auto", it will quit if the time of a test run exceeds 3x the average time it normally takes the particular test to complete its run.</p>
+<p>This module utilizes the following environmental variables: TEST_TIMEOUT_AFTER.</p>
 <h2>Timed Screenshot</h2>
 <p>This is a module that will take a screenshot of the system at a pre-defined interval. ImageMagick must be installed onto the system prior to using this module.</p>
 <p>This module utilizes the following environmental variables: SCREENSHOT_INTERVAL.</p>
 <h2>Toggle Screensaver</h2>
 <p>This module toggles the system's screensaver while the Phoronix Test Suite is running. At this time, the GNOME and KDE screensavers are supported.</p>
 <p>This module utilizes the following environmental variables: HALT_SCREENSAVER.</p>
+<h2>Linux Turbostat Dumper</h2>
+<p>Setting TURBOSTAT_LOG_DIR=_DIR_ will auto-load and enable this Phoronix Test Suite module. The module will -- if turbostat is installed on the system and the user is root -- allow dumping of the TurboStat data to the specified directly on a per-test basis. This allows easily collecting of turbostat logs for each test being run.</p>
+<p>This module utilizes the following environmental variables: TURBOSTAT_LOG_DIR.</p>
 <h2>Update Checker</h2>
 <p>This module checks to see if the Phoronix Test Suite -- and its tests and suites -- are up to date plus also handles message of the day information.</p>
 <h2>Utilize Wine On Linux Benchmarking</h2>
@@ -774,7 +796,7 @@ NOTE: Use the "system-sensors" command to see what sensors are available for mon
 <p>Without all of these extensions, some capabilities of the Phoronix Test Suite will not be available. Many of these packages are enabled by default and do not require any additional installation steps on most Linux distributions, otherwise they are often found in the package vendor's repository.</p>
 <h1>Notes</h1>
 <h2>General</h2>
-<p>You may need to modify the <em>php.ini</em> file on your system in order to support uploading results to OpenBenchmarking.org or logging into your OpenBenchmarking.org account. The <em>allow_url_fopen</em>, <em>file_uploads</em>, and <em>allow_url_include</em> options must be set to true in the PHP configuration. See additional information in this <a href="http://www.phoronix.com/forums/showpost.php?p=32484&amp;postcount=4">Phoronix Forums support thread</a>.</p>
+<p>You may need to modify the <em>php.ini</em> file on your system in order to support uploading results to OpenBenchmarking.org or logging into your OpenBenchmarking.org account. The <em>allow_url_fopen</em>, <em>file_uploads</em>, and <em>allow_url_include</em> options must be set to true in the PHP configuration.</p>
 <p>Major updates to the Phoronix Test Suite are released on a quarterly basis. The latest stable and development versions of the Phoronix Test Suite are available at <a href="http://www.phoronix-test-suite.com/">Phoronix-Test-Suite.com</a>. The Git repository where the latest Phoronix Test Suite code is provided is hosted at <a href="https://github.com/phoronix-test-suite/phoronix-test-suite">GitHub.com/phoronix-test-suite</a> and can be cloned/pulled from the <em>https://github.com/phoronix-test-suite/phoronix-test-suite.git</em> repository location. The latest upstream development code is housed in the master tree while older Phoronix Test Suite releases are available in their respective Git branches based upon the release's code-name.</p>
 <p>If building the PHP package from upstream sources, it should just be a matter of running <em>./configure</em> with the <em>--enable-zip</em> flag (all other requirements should be apart of the stock PHP configuration) to satisfy the PHP needs of the Phoronix Test Suite.</p>
 <h2>File Structure</h2>
@@ -791,6 +813,27 @@ NOTE: Use the "system-sensors" command to see what sensors are available for mon
 <p>The Phoronix Test Suite also supports *BSD operating systems. However, like the Solaris support, not all test profiles are compatible with BSD operating systems, but should run well on the likes of FreeBSD and DragonFlyBSD.</p>
 <h2>MacOS Installation</h2>
 <p>The Phoronix Test Suite is fully supported on Apple's macOS operating system. PHP ships with macOS by default so it's simply a matter of downloading the Phoronix Test Suite package, extracting it, and running the executable. For tests that rely upon a compiler, Apple's XCode with GCC and LLVM can be utilized.</p>
+<hr style="height: 50px; border: 0;"><a name="PhoronixTestSuiteOnWindows"></a><h1>Phoronix Test Suite On Windows</h1>
+
+<h2>Introduction</h2>
+<p>Phoronix Test Suite 8.0 features rewritten Windows support that is at a near feature parity to the program's long-standing support for Linux, macOS, BSD and Solaris operating systems. To make it abundantly clear, if you are using a Phoronix Test Suite version pre-8.0, you are best upgrading or ideally using Phoronix Test Suite Git as the Windows support remains in very active development at the moment as of early 2018.</p>
+<p>The Phoronix Test Suite Windows support currently targets <strong>Windows 10 x64</strong> and <strong>Windows Server 2016 x64</strong>. Earlier versions of Windows, namely Windows Server 2012 and Windows 8, may work to some extent but some hardware/software reporting features and other capabilities may be missing or report warning messages. The Phoronix Test Suite Windows support is also exclusively focused on x86 64-bit support: the Phoronix Test Suite itself will run on x86 32-bit but many of the program dependencies are configured for making use of 64-bit binaries.</p>
+<h2>Windows Setup / Dependencies</h2>
+<p>As with Phoronix Test Suite on Linux and other operating systems, the principal dependency is on PHP (PHP v5.3 or newer, including PHP 7.x). Running the <em>phoronix-test-suite.bat</em> file launcher for the Phoronix Test Suite on Windows will attempt to download and setup PHP on the system under <em>C:\PHP</em> as the default location should PHP support not be found within your system's <em>Program Files</em> directories. The PHP Windows build does depend upon Microsoft Visual C++ redistributable libraries, which the Windows launcher will also attempt to download and install if needed.</p>
+<p>The Phoronix Test Suite on Windows does depend upon <a href="https://www.cygwin.com/">Cygwin</a> for its Bash interpreter and other basic utilities to ease the process of porting test profiles to Windows with being able to use many of the same test installation scripts on Windows/Linux/macOS/BSD/Solaris then largely unmodified. Most of the Windows tests depend upon their respective native Windows applications/binaries while this Cygwin support is a convenience for handling these Bash setup scripts and also some test profiles that depend upon a GNU toolchain. The Phoronix Test Suite will attempt to download and setup Cygwin on the system if Cygwin isn't found in its default location of <em>C:\cygwin64</em>.</p>
+<p>Various test profiles may depend upon other "external dependencies" like Python, PERL, Steam, and Java, as examples. The Phoronix Test Suite as with its support for other operating systems and Linux distributions will attempt to install these needed dependencies on a per-test basis when needed if existing support is not detected on the system.</p>
+<h2>Running The Phoronix Test Suite On Windows</h2>
+<p>The Phoronix Test Suite can run from its local directory and does not need to be "installed" to a system path or any other "setup" process prior to execution. On a clean install of Windows 10 x64 or Windows Server 2016, deploying the Phoronix Test Suite is designed to be as easy and straight-forward as possible:</p>
+<p>1. Download the Phoronix Test Suite 8.0+ or <a href="https://github.com/phoronix-test-suite/phoronix-test-suite">Phoronix-Test-Suite from GitHub</a> (<a href="https://github.com/phoronix-test-suite/phoronix-test-suite/archive/master.zip">zip file</a>).</p>
+<p>2. From the Command Prompt or PowerShell, enter the <em>phoronix-test-suite</em> directory whether it be from Git or a zipped download.</p>
+<p>3. Run the <em>phoronix-test-suite.bat</em> file that should proceed to run the Phoronix Test Suite just as you would on any other operating system. If needed the Phoronix Test Suite will try to initially download and setup PHP if needed followed by the attempted automatic Cygwin setup, etc.</p>
+<p>4. Any of the Phoronix Test Suite commands from other operating systems should work on Windows. If you are new to the Phoronix Test Suite, you may enjoy a bit more guided experience by running the <strong>phoronix-test-suite shell</strong> command.</p>
+<h2>Test Profiles On Windows</h2>
+<p>As of March 2018, around 50 of the test profiles are currently compatible with the Phoronix Test Suite on Windows. This includes many of the popular benchmarks and other interesting test cases. Over time more test profiles will continue to be ported to Windows where applicable and there are also some Windows-only tests also supported for execution by the Phoronix Test Suite.</p>
+<h2>Getting Started</h2>
+<p>Besides <strong>phoronix-test-suite shell</strong> and <strong>phoronix-test-suite help</strong>, there is also <strong>phoronix-test-suite interactive</strong> for helping new users understand Phoronix Test Suite benchmarking. Long story short, it should be as easy as running <strong>phoronix-test-suite benchmark c-ray</strong> or <strong>phoronix-test-suite benchmark crafty</strong> as some examples for carrying out automated, cross-platform benchmarks in a side-by-side and fully-reproducible manner.</p>
+<h2>Support</h2>
+<p>Community technical support is available via <a href="https://github.com/phoronix-test-suite/phoronix-test-suite/issues">GitHub</a>. For enterprise inquiries, commercial support, and custom engineering services, <a href="http://phoronix-test-suite.com/?k=commercial">contact us</a>.</p>
 <hr style="height: 50px; border: 0;"><a name="ExternalDependencies"></a><h1>External Dependencies</h1>
 <p>The Phoronix Test Suite has a feature known as "External Dependencies" where the Phoronix Test Suite can attempt to automatically install some of the test-specific dependencies on supported distributions. If running on a distribution where there is currently no External Dependencies profile, the needed package name(s) are listed for manual installation.</p>
 <p>Below are a list of the operating systems that currently have external dependencies support within the Phoronix Test Suite for the automatic installation of needed test files.</p><hr><ul></ul><li>Alpine Linux</li><li>Amazon</li><li>Angstrom</li><li>Arch Linux</li><li>Clear Linux</li><li>ClearOS</li><li>ClearOS Core Server</li><li>Debian</li><li>DragonFlyBSD</li><li>Fedora</li><li>Fluxbuntu</li><li>GNU KFreeBSD</li><li>Gentoo</li><li>Goobuntu</li><li>HP</li><li>Joli Cloud</li><li>Linaro</li><li>Linux Embedded Development Environment</li><li>Linux Mint</li><li>MEPIS</li><li>Mac OS X</li><li>MacPorts</li><li>Mageia</li><li>Mandriva</li><li>MeeGo</li><li>Microsoft Windows</li><li>MidnightBSD</li><li>Moblin</li><li>Mythbuntu</li><li>NetBSD</li><li>Nexenta Core</li><li>OLPC</li><li>OpenIndiana</li><li>OpenMandriva</li><li>OpenMandrivaLinux</li><li>OpenSolaris</li><li>OpenSuSE</li><li>Optware</li><li>Oracle Server</li><li>PCLinuxOS</li><li>Palm</li><li>Pardus Linux</li><li>Red Hat Enterprise</li><li>Red Hat Enterprise Server</li><li>SUSE</li><li>SUSE Linux</li><li>Scientific</li><li>ScientificSL</li><li>Solus</li><li>Solus Linux</li><li>Termux</li><li>Ubuntu</li><li>Void Linux</li><li>Zenwalk</li><li>gNewSense</li><li>macOS Brew</li>
@@ -813,6 +856,8 @@ NOTE: Use the "system-sensors" command to see what sensors are available for mon
 <p><strong>~/.phoronix-test-suite/test-suites/</strong></p>
 <p>This is the directory where test suites are stored.</p>
 <h1>Environment Variables</h1>
+<p><strong>TEST_TIMEOUT_AFTER</strong></p>
+<p>When this variable is set, the value will can be set to <em>auto</em> or a positive integer. The value indicates the number of minutes until a test run should be aborted, such as for a safeguard against hung/deadlocked processes or other issues. Setting this to a high number as a backup would be recommended for fending off possible hangs / stalls in the testing process if the test does not quit. If the value is <em>auto</em>, it will quit if the time of a test run exceeds 3x the average time it normally takes the particular test to complete its run. In the future, auto might be enabled by default in a future PTS release.</p>
 <p><strong>TEST_RESULTS_NAME</strong></p>
 <p>When this variable is set, the value will be used as the name for automatically saving the test results.</p>
 <p><strong>TEST_RESULTS_IDENTIFIER</strong></p>
@@ -879,18 +924,19 @@ NOTE: Use the "system-sensors" command to see what sensors are available for mon
 <p>If Phodevi fails to detect the system's monitor standard / default resolution, the mode can be specified in this variable. Example: <em>DEFAULT_VIDEO_MODE=1680x1050 phoronix-test-suite benchmark nexuiz</em>.</p>
 <p><strong>SKIP_EXTERNAL_DEPENDENCIES</strong></p>
 <p>To skip the Phoronix Test Suite external dependency checking/installation when installing a test, set this environment variable to <em>1</em>. If wishing to skip only certain external dependencies, set this variable's value to the name of the external dependencies (the generic dependency names used by the Phoronix Test Suite) to not install. Multiple dependencies to skip can be delimited by a comma.</p>
+<p><strong>PTS_EXTRA_SYSTEM_LOGS_DIR</strong></p>
+<p>By default the Phoronix Test Suite collects common system logs (cpuinfo, lscpu, dmesg) during the benchmarking process when saving test results. If wanting to collect additional, arbitrary system log files specific to your operating environment or for other niche system information, the <em>PTS_EXTRA_SYSTEM_LOGS_DIR</em> environment variable can be set as a path to a directory containing such log files. Prior to running the Phoronix Test Suite simply set <em>PTS_EXTRA_SYSTEM_LOGS_DIR</em> to the directory where any text files should be captured from following test completion.</p>
 <hr style="height: 50px; border: 0;"><a name="GeneralInformation"></a><h1>General Information</h1>
 <h1>Frequently Asked Questions</h1>
 <p><strong><em>Q:</em> May I use the Phoronix Test Suite when running benchmarks for my own publication or blog? Are there any publishing restrictions?</strong></p>
 <p><strong>A:</strong> Anyone is more than welcome to use the Phoronix Test Suite for their own publication or purpose. While the Phoronix Test Suite came out of our internal test tools for carrying out Linux hardware reviews at <a href="http://www.phoronix.com/">Phoronix.com</a>, we invite other hardware review web-sites, technology journals, and independent publications to use our software too. While not required, we would just kindly ask that you mention in your review/article that the <em>Phoronix Test Suite</em> was used for carrying out your testing, and ideally to link to <a href="http://www.phoronix-test-suite.com/">www.phoronix-test-suite.com</a> so that your readers will know where to obtain the software if they are interested in running the tests. You are also more than welcome to upload your results to <a href="http://www.openbenchmarking.org/">OpenBenchmarking.org</a> so that others may compare their results against yours in an easy manner.</p>
 <p>We also try to make the Phoronix Test Suite easy-to-use by independent publications. For example, if you would like to watermark your web-site's URL into the graphs containing your test results, that can be easily modified in <em>~/.phoronix-test-suite/graph-config.json</em>. The colors and other graph settings are also stored in this XML file. If you are a publication and run into any issues with the Phoronix Test Suite or have a feature request, please let us know.</p>
-<p>A partial list of other publications using the Phoronix Test Suite can be found in <a href="http://www.phoronix.com/forums/showthread.php?t=12925">this forum thread</a>.</p>
 <p><strong><em>Q:</em> Why does the Phoronix Test Suite not use my distribution's package management system for acquiring all needed packages?</strong></p>
 <p><strong>A:</strong> The tests themselves are generally downloaded from source and built locally on the machine, rather than fetching any distribution-specific packages. This is done to ensure more comparable results across operating systems / releases, etc. The distribution packager could be applying a number of unknown patches to the software, building the software with unique build options, or making other changes to the software that could skew the results.</p>
 <p><strong><em>Q:</em> Besides being a developer, documentation writer, or having any other unique technical abilities, how else can I contribute to the Phoronix Test Suite?</strong></p>
-<p><strong>A:</strong> Independent code contributions are very welcome as well as creating your own test profiles and suites. We also appreciate any feedback, comments, or other ideas either by emailing us, posting on the forums, or sending a message to the mailing list. You can also see this (outdated) <a href="http://www.phoronix.com/forums/showthread.php?t=16180">forum thread</a>.</p>
+<p><strong>A:</strong> Independent code contributions are very welcome as well as creating your own test profiles and suites. We also appreciate any feedback, comments, or other ideas either by emailing us, posting on GitHub, or sending a message to the mailing list.</p>
 <p><strong><em>Q:</em> Do you offer technical support for the Phoronix Test Suite</strong></p>
-<p><strong>A:</strong> Paid, professional support is available and is done via <a href="http://commercial.phoronix-test-suite.com/">our commercial services</a>. We also offer Phoromatic licenses for use within a corporate intranet and other custom services. Free, community support is offered via our <a href="http://phoronix-test-suite.com/mailman/listinfo/trondheim-pts_phoronix-test-suite.com">mailing list</a>, IRC channel (<em>#phoronix</em> on <em>FreeNode.net</em>, and the <a href="http://www.phoronix.com/forums/">Phoronix Forums</a>.</p>
+<p><strong>A:</strong> Paid, professional support is available and is done via <a href="http://commercial.phoronix-test-suite.com/">our commercial services</a>. We also offer Phoromatic licenses for use within a corporate intranet and other custom services. Free, community support is offered via our <a href="http://phoronix-test-suite.com/mailman/listinfo/trondheim-pts_phoronix-test-suite.com">mailing list</a>, IRC channel (<em>#phoronix</em> on <em>FreeNode.net</em>, and <a href="https://github.com/phoronix-test-suite">GitHub</a>.</p>
 <p><strong><em>Q:</em> May I put the Phoronix Test Suite logo on my company's web-site or on my product packaging?</strong></p>
 <p><strong>A:</strong> <a href="http://www.phoronix-test-suite.com/?k=contact">Contact us</a> for licensing information and details regarding the Phoronix Certification &amp; Qualification Suite.</p>
 <p><strong><em>Q:</em> How often is the Phoronix Test Suite updated?</strong></p>
@@ -928,69 +974,117 @@ In the event that a test profile fails to install or run, the following general
 <hr style="height: 50px; border: 0;"><a name="VirtualTestSuites"></a><h1>Virtual Test Suites</h1>
 <p>Virtual test suites are not like a traditional test suite defined by the XML suite specification. Virtual test suites are dynamically generated in real-time by the Phoronix Test Suite client based upon the specified test critera. Virtual test suites can automatically consist of all test profiles that are compatible with a particular operating system or test profiles that meet other critera. When running a virtual suite, the OpenBenchmarking.org repository of the test profiles to use for generating the dynamic suite must be prefixed. </p>
 <p>Virtual test suites can be installed and run just like a normal XML test suite and shares nearly all of the same capabilities. However, when running a virtual suite, the user will be prompted to input any user-configuration options for needed test profiles just as they would need to do if running the test individually. When running a virtual suite, the user also has the ability to select individual tests within the suite to run or to run all of the contained test profiles. Virtual test suites are also only supported for an OpenBenchmarking.org repository if there is no test profile or test suite of the same name in the repository. Below is a list of common virtual test suites for the main Phoronix Test Suite repository, but the dynamic list of available virtual test suites based upon the enabled repositories is available by running <em>phoronix-test-suite list-available-virtual-suites.</em></p><hr>
-<h3>All PTS Tests<em>  pts/all</em>
+<h3>All Tests In Pts<em>  pts/all</em>
 </h3>
-<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.</p>
+<p>This is a collection of all supported test profiles found within the specified OpenBenchmarking.org repository.</p>
+<h3>Application Tests<em>  pts/application</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a application software test.</p>
+<h3>Benchmark Tests<em>  pts/benchmark</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a benchmark software test.</p>
+<h3>BLAS (Basic Linear Algebra Sub-Routine) Tests<em>  pts/blas</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on BLAS (Basic Linear Algebra Sub-Routine)</p>
+<h3>C++ Boost Tests<em>  pts/boost</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on C++ Boost</p>
+<h3>Bsd Operating System Tests<em>  pts/bsd</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the bsd Operating System.</p>
+<h3>Disk Subsystem Tests<em>  pts/disk</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the disk sub-system.</p>
+<h3>Everything In Pts<em>  pts/everything</em>
+</h3>
+<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository, including unsupported tests, etc.</p>
+<h3>Fortran Tests<em>  pts/fortran</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on Fortran</p>
+<h3>Game Tests<em>  pts/game</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a game software test.</p>
+<h3>Go Language Tests<em>  pts/golang</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on Go Language</p>
+<h3>Graphics Subsystem Tests<em>  pts/graphics</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the graphics sub-system.</p>
 <h3>Installed Tests<em>  pts/installed</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.</p>
-<h3>Every PTS Test<em>  pts/everything</em>
+<h3>Java Tests<em>  pts/java</em>
 </h3>
-<p>This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing java.</p>
+<h3>LAPACK (Linear Algebra Pack) Tests<em>  pts/lapack</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on LAPACK (Linear Algebra Pack)</p>
 <h3>Linux Operating System Tests<em>  pts/linux</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.</p>
-<h3>Solaris Operating System Tests<em>  pts/solaris</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the linux Operating System.</p>
+<h3>Macosx Operating System Tests<em>  pts/macosx</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.</p>
-<h3>BSD Operating System Tests<em>  pts/bsd</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the macosx Operating System.</p>
+<h3>Memory Subsystem Tests<em>  pts/memory</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.</p>
-<h3>MacOSX Operating System Tests<em>  pts/macosx</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the memory sub-system.</p>
+<h3>Network Subsystem Tests<em>  pts/network</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.</p>
-<h3>Windows Operating System Tests<em>  pts/windows</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the network sub-system.</p>
+<h3>Node.js + NPM Tests<em>  pts/node-npm</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.</p>
-<h3>Hurd Operating System Tests<em>  pts/hurd</em>
+<p>This is a collection of test profiles having an external dependency on Node.js + NPM</p>
+<h3>OpenCV Tests<em>  pts/opencv</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.</p>
-<h3>System Subsystem Tests<em>  pts/system</em>
+<p>This is a collection of test profiles having an external dependency on OpenCV</p>
+<h3>Openmpi Tests<em>  pts/openmpi</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmpi.</p>
+<h3>Os Subsystem Tests<em>  pts/os</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the os sub-system.</p>
 <h3>Processor Subsystem Tests<em>  pts/processor</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.</p>
-<h3>Graphics Subsystem Tests<em>  pts/graphics</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the processor sub-system.</p>
+<h3>Python Tests<em>  pts/python</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.</p>
-<h3>Other Subsystem Tests<em>  pts/other</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing python.</p>
+<h3>Ruby Tests<em>  pts/ruby</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.</p>
-<h3>Utility Tests<em>  pts/utility</em>
+<p>This is a collection of test profiles having an external dependency on Ruby</p>
+<h3>Rust Tests<em>  pts/rust</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.</p>
-<h3>Simulator Tests<em>  pts/simulator</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.</p>
+<p>This is a collection of test profiles having an external dependency on Rust</p>
 <h3>Scientific Tests<em>  pts/scientific</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.</p>
-<h3>Benchmark Tests<em>  pts/benchmark</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a scientific software test.</p>
+<h3>Simulator Tests<em>  pts/simulator</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.</p>
-<h3>Application Tests<em>  pts/application</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a simulator software test.</p>
+<h3>Solaris Operating System Tests<em>  pts/solaris</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.</p>
-<h3>Game Tests<em>  pts/game</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the solaris Operating System.</p>
+<h3>System Subsystem Tests<em>  pts/system</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the system sub-system.</p>
+<h3>Utility Tests<em>  pts/utility</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a utility software test.</p>
+<h3>Windows Operating System Tests<em>  pts/windows</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the windows Operating System.</p>
 <h3>Smp Tests<em>  pts/smp</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.</p>
+<h3>Opencl Tests<em>  pts/opencl</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing opencl.</p>
 <h3>Cuda Tests<em>  pts/cuda</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cuda.</p>
+<h3>Mpi Tests<em>  pts/mpi</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing mpi.</p>
 <h3>Openmp Tests<em>  pts/openmp</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmp.</p>
@@ -1003,6 +1097,9 @@ In the event that a test profile fails to install or run, the following general
 <h3>Go Tests<em>  pts/go</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing go.</p>
+<h3>Optix Tests<em>  pts/optix</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing optix.</p>
 <h3>Vdpau Tests<em>  pts/vdpau</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing vdpau.</p>
@@ -1012,303 +1109,111 @@ In the event that a test profile fails to install or run, the following general
 <h3>Responsiveness Tests<em>  pts/responsiveness</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing responsiveness.</p>
-<h3>Openmpi Tests<em>  pts/openmpi</em>
+<h3>All Tests In System<em>  system/all</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmpi.</p>
-<h3>All SYSTEM Tests<em>  system/all</em>
+<p>This is a collection of all supported test profiles found within the specified OpenBenchmarking.org repository.</p>
+<h3>Application Tests<em>  system/application</em>
 </h3>
-<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a application software test.</p>
+<h3>Benchmark Tests<em>  system/benchmark</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a benchmark software test.</p>
+<h3>BLAS (Basic Linear Algebra Sub-Routine) Tests<em>  system/blas</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on BLAS (Basic Linear Algebra Sub-Routine)</p>
+<h3>C++ Boost Tests<em>  system/boost</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on C++ Boost</p>
+<h3>Bsd Operating System Tests<em>  system/bsd</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the bsd Operating System.</p>
+<h3>Disk Subsystem Tests<em>  system/disk</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the disk sub-system.</p>
+<h3>Everything In System<em>  system/everything</em>
+</h3>
+<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository, including unsupported tests, etc.</p>
+<h3>Game Tests<em>  system/game</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a game software test.</p>
+<h3>Graphics Subsystem Tests<em>  system/graphics</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the graphics sub-system.</p>
 <h3>Installed Tests<em>  system/installed</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.</p>
-<h3>Every SYSTEM Test<em>  system/everything</em>
-</h3>
-<p>This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.</p>
 <h3>Linux Operating System Tests<em>  system/linux</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.</p>
-<h3>Solaris Operating System Tests<em>  system/solaris</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the linux Operating System.</p>
+<h3>Macosx Operating System Tests<em>  system/macosx</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.</p>
-<h3>BSD Operating System Tests<em>  system/bsd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.</p>
-<h3>MacOSX Operating System Tests<em>  system/macosx</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.</p>
-<h3>Windows Operating System Tests<em>  system/windows</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.</p>
-<h3>Hurd Operating System Tests<em>  system/hurd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.</p>
-<h3>System Subsystem Tests<em>  system/system</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.</p>
-<h3>Processor Subsystem Tests<em>  system/processor</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.</p>
-<h3>Disk Subsystem Tests<em>  system/disk</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Disk sub-system.</p>
-<h3>Graphics Subsystem Tests<em>  system/graphics</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.</p>
-<h3>Memory Subsystem Tests<em>  system/memory</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Memory sub-system.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the macosx Operating System.</p>
 <h3>Network Subsystem Tests<em>  system/network</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Network sub-system.</p>
-<h3>Other Subsystem Tests<em>  system/other</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the network sub-system.</p>
+<h3>OpenCV Tests<em>  system/opencv</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.</p>
-<h3>Utility Tests<em>  system/utility</em>
+<p>This is a collection of test profiles having an external dependency on OpenCV</p>
+<h3>OpenMPI Tests<em>  system/openmpi</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.</p>
-<h3>Simulator Tests<em>  system/simulator</em>
+<p>This is a collection of test profiles having an external dependency on OpenMPI</p>
+<h3>Processor Subsystem Tests<em>  system/processor</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the processor sub-system.</p>
+<h3>Python Tests<em>  system/python</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on Python</p>
 <h3>Scientific Tests<em>  system/scientific</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.</p>
-<h3>Benchmark Tests<em>  system/benchmark</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a scientific software test.</p>
+<h3>Solaris Operating System Tests<em>  system/solaris</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.</p>
-<h3>Application Tests<em>  system/application</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the solaris Operating System.</p>
+<h3>System Subsystem Tests<em>  system/system</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.</p>
-<h3>Game Tests<em>  system/game</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the system sub-system.</p>
+<h3>Utility Tests<em>  system/utility</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a utility software test.</p>
+<h3>Windows Operating System Tests<em>  system/windows</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the windows Operating System.</p>
 <h3>Opencl Tests<em>  system/opencl</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing opencl.</p>
 <h3>Cuda Tests<em>  system/cuda</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cuda.</p>
-<h3>All GIT Tests<em>  git/all</em>
+<h3>Smp Tests<em>  system/smp</em>
 </h3>
-<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.</p>
-<h3>Installed Tests<em>  git/installed</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.</p>
+<h3>All Tests In Git<em>  git/all</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.</p>
-<h3>Every GIT Test<em>  git/everything</em>
+<p>This is a collection of all supported test profiles found within the specified OpenBenchmarking.org repository.</p>
+<h3>Bsd Operating System Tests<em>  git/bsd</em>
 </h3>
-<p>This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the bsd Operating System.</p>
+<h3>Everything In Git<em>  git/everything</em>
+</h3>
+<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository, including unsupported tests, etc.</p>
 <h3>Linux Operating System Tests<em>  git/linux</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.</p>
-<h3>Solaris Operating System Tests<em>  git/solaris</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the linux Operating System.</p>
+<h3>Macosx Operating System Tests<em>  git/macosx</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.</p>
-<h3>BSD Operating System Tests<em>  git/bsd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.</p>
-<h3>MacOSX Operating System Tests<em>  git/macosx</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.</p>
-<h3>Windows Operating System Tests<em>  git/windows</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.</p>
-<h3>Hurd Operating System Tests<em>  git/hurd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.</p>
-<h3>System Subsystem Tests<em>  git/system</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the macosx Operating System.</p>
 <h3>Processor Subsystem Tests<em>  git/processor</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.</p>
-<h3>Disk Subsystem Tests<em>  git/disk</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the processor sub-system.</p>
+<h3>Rust Tests<em>  git/rust</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Disk sub-system.</p>
-<h3>Graphics Subsystem Tests<em>  git/graphics</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.</p>
-<h3>Memory Subsystem Tests<em>  git/memory</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Memory sub-system.</p>
-<h3>Network Subsystem Tests<em>  git/network</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Network sub-system.</p>
-<h3>Other Subsystem Tests<em>  git/other</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.</p>
+<p>This is a collection of test profiles having an external dependency on Rust</p>
 <h3>Utility Tests<em>  git/utility</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.</p>
-<h3>Simulator Tests<em>  git/simulator</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.</p>
-<h3>Scientific Tests<em>  git/scientific</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.</p>
-<h3>Benchmark Tests<em>  git/benchmark</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.</p>
-<h3>Application Tests<em>  git/application</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.</p>
-<h3>Game Tests<em>  git/game</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a utility software test.</p>
 <h3>Smp Tests<em>  git/smp</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.</p>
-<h3>All PTS Tests<em>  pts/all</em>
-</h3>
-<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.</p>
-<h3>Installed Tests<em>  pts/installed</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.</p>
-<h3>Every PTS Test<em>  pts/everything</em>
-</h3>
-<p>This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.</p>
-<h3>Linux Operating System Tests<em>  pts/linux</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.</p>
-<h3>Solaris Operating System Tests<em>  pts/solaris</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.</p>
-<h3>BSD Operating System Tests<em>  pts/bsd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.</p>
-<h3>MacOSX Operating System Tests<em>  pts/macosx</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.</p>
-<h3>Windows Operating System Tests<em>  pts/windows</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.</p>
-<h3>Hurd Operating System Tests<em>  pts/hurd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.</p>
-<h3>System Subsystem Tests<em>  pts/system</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.</p>
-<h3>Processor Subsystem Tests<em>  pts/processor</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.</p>
-<h3>Graphics Subsystem Tests<em>  pts/graphics</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.</p>
-<h3>Other Subsystem Tests<em>  pts/other</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.</p>
-<h3>Utility Tests<em>  pts/utility</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.</p>
-<h3>Simulator Tests<em>  pts/simulator</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.</p>
-<h3>Scientific Tests<em>  pts/scientific</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.</p>
-<h3>Benchmark Tests<em>  pts/benchmark</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.</p>
-<h3>Application Tests<em>  pts/application</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.</p>
-<h3>Game Tests<em>  pts/game</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.</p>
-<h3>Smp Tests<em>  pts/smp</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.</p>
-<h3>Cuda Tests<em>  pts/cuda</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cuda.</p>
-<h3>Openmp Tests<em>  pts/openmp</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmp.</p>
-<h3>Cloud Tests<em>  pts/cloud</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cloud.</p>
-<h3>Docker Tests<em>  pts/docker</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing docker.</p>
-<h3>Go Tests<em>  pts/go</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing go.</p>
-<h3>Vdpau Tests<em>  pts/vdpau</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing vdpau.</p>
-<h3>Video Tests<em>  pts/video</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing video.</p>
-<h3>Responsiveness Tests<em>  pts/responsiveness</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing responsiveness.</p>
-<h3>Openmpi Tests<em>  pts/openmpi</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmpi.</p>
-<h3>All WINDOWS Tests<em>  windows/all</em>
-</h3>
-<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.</p>
-<h3>Installed Tests<em>  windows/installed</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.</p>
-<h3>Every WINDOWS Test<em>  windows/everything</em>
-</h3>
-<p>This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.</p>
-<h3>Linux Operating System Tests<em>  windows/linux</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.</p>
-<h3>Solaris Operating System Tests<em>  windows/solaris</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.</p>
-<h3>BSD Operating System Tests<em>  windows/bsd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.</p>
-<h3>MacOSX Operating System Tests<em>  windows/macosx</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.</p>
-<h3>Windows Operating System Tests<em>  windows/windows</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.</p>
-<h3>Hurd Operating System Tests<em>  windows/hurd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.</p>
-<h3>System Subsystem Tests<em>  windows/system</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.</p>
-<h3>Processor Subsystem Tests<em>  windows/processor</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.</p>
-<h3>Disk Subsystem Tests<em>  windows/disk</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Disk sub-system.</p>
-<h3>Graphics Subsystem Tests<em>  windows/graphics</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.</p>
-<h3>Memory Subsystem Tests<em>  windows/memory</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Memory sub-system.</p>
-<h3>Network Subsystem Tests<em>  windows/network</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Network sub-system.</p>
-<h3>Other Subsystem Tests<em>  windows/other</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.</p>
-<h3>Utility Tests<em>  windows/utility</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.</p>
-<h3>Simulator Tests<em>  windows/simulator</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.</p>
-<h3>Scientific Tests<em>  windows/scientific</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.</p>
-<h3>Benchmark Tests<em>  windows/benchmark</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.</p>
-<h3>Application Tests<em>  windows/application</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.</p>
-<h3>Game Tests<em>  windows/game</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.</p>
 <hr style="height: 50px; border: 0;"><a name="ComponentTesting"></a><h1>Component Testing</h1>
 <h1>Compiler Testing &amp; Masking</h1>
 <p>A majority of the test profiles provided by OpenBenchmarking.org to the Phoronix Test Suite are source-based tests. Relying upon the upstream source-code for each program under test allows for the tests to be easily brought to new platforms and architectures, avoids any out-of-tree / non-default packaging differences by different distributions and operating systems, and to allow the Phoronix Test Suite user to easily test new compilers and/or compiler options. For the source-based tests, the Phoronix Test Suite relies upon a compiler (e.g. GCC, LLVM/Clang, Sun Studio, Open64, et al) being present on the system under test. The Phoronix Test Suite does respect <em>CC/CXX</em> environment variables and test profiles are expected to honor <em>CFLAGS/CXXFLAGS</em> and other compiler settings.</p>
@@ -1319,9 +1224,90 @@ In the event that a test profile fails to install or run, the following general
 <h1>Disk / File-System Testing</h1>
 <p>By default tests are installed to <em>~/.phoronix-test-suite/installed-tests/</em>. However, the location can be updated from <em>~/.phoronix-test-suite/user-config.xml</em> or dynamically via the <em>PTS_TEST_INSTALL_ROOT_PATH</em> environment variable.</p>
 <p>When any disk tests are executed, the Phoronix Test Suite will attempt to log the mount options and scheduler of the disk/partition being used for testing. This information is subsequently displayed within the system information table. If the scheduler / mount options are maintained the same throughout all test runs, only a single line is displayed otherwise the options for each test run will be automatically displayed. The file-system in use is always captured and shown in the system information table.</p>
-<hr style="height: 50px; border: 0;"><a name="Phoromatic"></a><h1>Phoromatic</h1>
-<h1>Overview</h1>
-<p>The Phoronix Test Suite now features its own built-in Phoromatic server and client implementations. See the <em>phoromatic.pdf</em> / <em>phoromatic.html</em> documentation for more information on this advanced capability.</p>
+<hr style="height: 50px; border: 0;"><a name="PhoronixTestSuitePhoromatic"></a><h1>Phoronix Test Suite Phoromatic</h1>
+<h1>Phoromatic Server</h1>
+<h2>Introduction</h2>
+<p>Phoromatic is a remote management system for the Phoronix Test Suite. Phoromatic allows the automatic (hence the name <em>Phoro-matic</em>) scheduling of tests, remote installation of new tests, and the management of multiple test systems all through an intuitive, easy-to-use web interface. Tests can be scheduled to automatically run on a routine basis across multiple test systems. The test results are then available from this central, secure location.</p>
+<p>Phoromatic was originally introduced with Phoronix Test Suite 2.0 via Phoromatic.com as a project going back to 2008~2009. Phoromatic.com debuted as a hosted instance with the option of behind-the-firewall licensing for use within organizations. With Phoronix Test Suite 5.2 the model shifted to offer a local, open-source version of Phoromatic built into the Phoronix Test Suite code-base. Thanks to continued enterprise development, with Phoronix Test Suite 5.4 is now a fully-functioning, built-in version of Phoromatic that's open-source and can be used for behind-the-firewall testing without needing to push results to OpenBenchmarking.org and the ability to keep all results private.</p>
+<p>Phoromatic in Phoronix Test Suite 5.4 also has the ability to support zero-conf  network discovery using Avahi and the automatic distribution of needed test profiles/suites and test files. Phoronix Test Suite 5.4's Phoromatic is a significant breakthrough for open-source testing particularly those running this GPL benchmarking software within test labs and other large organizations.</p>
+<h2>Features</h2>
+<p>Built atop the Phoronix Test Suite, Phoromatic offers many features for both enterprise and community/personal users:</p>
+<h3>Automated Scheduling</h3>
+<p>Whether it is every evening at 6:00PM, once every Thursday at 10:00AM or somewhere in between, Phoromatic can schedule tests to be run at user-defined intervals. The testing schedules can be updated through Phoromatic web interface. After the test(s) have run, the results will be immediately uploaded to Phoromatic.</p>
+<h3>Extensible</h3>
+<p>Any test profile or test suite that is compliant with the Phoronix Test Suite specification will work with Phoromatic. Phoromatic is able to leverage the hundreds of test profiles and test suites currently in the Phoronix Test Suite via OpenBenchmarking.org, along with any custom or proprietary test profiles you or your company utilize. Additionally, the Phoromatic interface allows the user to construct their own test suite(s).</p>
+<h3>Remote Testing</h3>
+<p>Once the test system is setup, all testing and management of that system can be done remotely. There is no need to execute Phoronix Test Suite commands locally using the GUI or command line version, but instead nearly all of the same features are accessible from the Phoromatic interface.</p>
+<h3>Multi-System Support</h3>
+<p>A single Phoromatic account is able to manage multiple test systems running the Phoronix Test Suite. Phoromatic supports grouping together test systems, tagging, and other features to support effectively managing many test systems. From the Phoromatic interface, installed system hardware and software from a given system can also be viewed.</p>
+<h3>Turn-Key Deployment</h3>
+<p>No additional software needs to be installed to support Phoromatic; all that's needed is Phoronix Test Suite 5.4 or later for full compatibility. New test systems can easily be synced with a given Phoromatic account by running a single command from the Phoronix Test Suite client.</p>
+<h3>Result Management</h3>
+<p>Test results are automatically uploaded to the Phoromatic account and remain private unless you opt to upload them to OpenBenchmarking.org. From the Phoromatic interface, results from multiple test systems can easily be compared and multiple results from the same systems can be used to track performance over time. There are also options to look at the statistical significance of the results and other features to efficiently and effectively analyze the system's performance.</p>
+<h3>Decentralized</h3>
+<p>Once the Phoronix Test Suite running on the Phoromatic Server has been able to cache all of the OpenBenchmarking.org test files and the needed files for each test, Phoromatic with any Phoronix Test Suite clients on your LAN can run fully decentralized without the need for a constant stream of OpenBenchmarking.org communication or Internet connection for that matter. (The only exception would be if your local systems don't have all their needed external dependencies and your system's package manager would need to install components like a compiler or necessary system libraries.</p>
+<h3>Fully Open-Source</h3>
+<p>Phoromatic is now fully open-source within the Phoronix Test Suite code-base for fostering greater development and new capabilities. Patches are welcome and Phoronix Media is available to provide commercial support and custom engineering services around Phoromatic and the Phoronix Test Suite.</p>
+<h2>Phoromatic Server Setup</h2>
+<p>Phoromatic is built into the Phoronix Test Suite code-base and should be found in all packaged versions of the <strong>phoronix-test-suite</strong>. Starting the Phoromatic Server entails running phoronix-test-suite start-phoromatic-server after configuring the server information within <em>~/.phoronix-test-suite/user-config.xml</em>. The Phoromatic Server can with or without root permissions depending upon your firewall and the port numbers you wish to use for the server.</p>
+<p>On the "client side", any up-to-date version of the Phoronix Test Suite can automatically communicate with the Phoromatic Server. If Avahi support is available (commonly in Linux distribution repositories as <u>avahi-tools</u>), there should be zero-conf discovery if the Phoromatic Server and client systems are on the same LAN. If a Phoronix Test Suite client discovers a Phoromatic Server, it will attempt to use it automatically as a local download cache. In the event of no Internet connection, it will also attempt to obtain the needed OpenBenchmarking.org test/suite meta-data from the Phoromatic Server based upon its archived meta-data. This allows the Phoronix Test Suite / Phoromatic deployment on the LAN to be self-sustaining without an Internet connection as long as the systems have all installed test dependencies.</p>
+<p>Further configuration of the setup parameters for the Phoromatic Server and Phoronix Test Suite clients can be tuned via the <em>~/.phoronix-test-suite/user-config.xml</em> file. All control and configuration of the Phoromatic Server is done via the web-based interface when the Phoromatic Server is active.</p>
+<p>The Phoromatic Server utilizes PHP/HHVM's built-in web-server capabilities and there's also a Phoronix Test Suite built-in WebSocket server that's also initiated for back-end processing. At this time there are no ports set by default for these services but must be defined within the user configuration file. With the Avahi zero-conf network discovery and other automated detection in place, there's little restrictions over the port selection.</p>
+<p>Systemd and Upstart service files are shipped with the Phoronix Test Suite for those that wish to have the services automatically run as daemons. The only new requirements over the basic Phoronix Test Suite system requirements is having PHP-SQLite support installed and the newer version of PHP or HHVM is recommended for offering the best support.</p>
+<h2>Example Deployments</h2>
+<h3>Use Case A: Unrestricted Internet Access, Local Result Storage</h3>
+<p>Systems on your network with unrestricted Internet access is the easiest and simplest deployment for the Phoronix Test Suite and Phoromatic. After installing the Phoronix Test Suite on the system you wish to designate the Phoromatic Server and have configured the <em>user-config.xml</em> file, simply run:</p>
+<p><strong>$ phoronix-test-suite start-phoromatic-server</strong></p>
+<p>Assuming you have no firewall or permission issues, the built-in web server and WebSocket server should proceed to initiate along with outputting the IP/port information for these services. Unless otherwise disabled from the user configuration file and if avahi-tools is present, the Phoromatic Server will be advertised with Avahi for zero-configuration networking.</p>
+<p>From the Phoromatic web interface you are able to create an account and from there proceed with the creating of test schedules, updating settings, and connecting systems. From the "client systems" you wish to use as the benchmarking nodes, it's simply a matter of running <strong>phoronix-test-suite phoromatic.connect</strong> with zero-conf networking or otherwise follow the information from the Phoromatic web interface for manual setup with the IP/port information.</p>
+<h3>Use Case B: No Internet Available To Client Systems</h3>
+<p>It's possible to run the Phoronix Test Suite and Phoromatic Server without a persistent Internet connection as long as you are able to first download the necessary files to the Phoromatic Server. After installing the Phoronix Test Suite on the system you wish to designate the Phoromatic Server and have configured the <em>user-config.xml</em> file, a few commands from the system while having an Internet connection will be able to cache the needed data:</p>
+<p><strong>$ phoronix-test-suite make-download-cache x264 xonotic ffmpeg</strong></p>
+<p>This command will simply download all of the needed test files for the tests/suites passed to the sub-command. Alternatively you could also pass pts/all to cache all tests. It's important though to just cache the tests/suites you'll be using on your network. This will generate the test file download cache by default to <em>~/.phoronix-test-suite/download-cache/</em> or <em>/usr/share/phoronix-test-suite/download-cache/</em> depending upon your write permissions. You can always run this command later with more test files. Alternatively, if you already have a number of tests installed on the system, simply running "phoronix-test-suite make-download-cache" will generate the cache based upon the currently installed tests.</p>
+<p><strong>$ phoronix-test-suite make-openbenchmarking-cache</strong></p>
+<p>This command will cache as much of the OpenBenchmarking.org meta-data as possible for test profiles and test suites. After the above commands, the Phoromatic Server should no longer need a persistent Internet connection.</p>
+<p><strong>$ phoronix-test-suite start-phoromatic-server</strong></p>
+<p>Proceed to start the Phoromatic Server and operate as normal.</p>
+<p>For the test clients without an Internet connection, as long as they're able to reach the Phoromatic Server, the Phoromatic Server should be able to automatically serve all of the needed test files download cache and OpenBenchmarking.org meta-data to the systems locally.</p>
+<h3>Use Case C: Phoromatic Across The Internet</h3>
+<p>If wishing to use the same Phoromatic Server across multiple geographic locations, it's easily possible -- you just lose out on the zero-conf networking ability. To let the Phoronix Test Suite client systems know about the remote Phoromatic Server, simply add the Phoromatic Server information to the client's <em>PhoromaticServers</em> element within the <em>user-config.xml</em>. Of course, make sure the Phoromatic Server has a globally resolvable IP address and its Phoromatic HTTP/WebSocket ports are open. Once informing the client of the Phoromatic Server, the use cases as above apply in the same manner.</p>
+<h2>Client Setup</h2>
+<p>From Phoronix Test Suite client systems running on the LAN, the following command will report all available detected Phoromatic Servers along with important server and debugging information:</p>
+<p><strong>$ phoronix-test-suite phoromatic.explore</strong></p>
+<p>With the following example output on finding one successful server:</p>
+<p><em>IP: 192.168.1.211<br>
+HTTP PORT: 5447<br>
+WEBSOCKET PORT: 5427<br>
+SERVER: PHP 5.5.9-1ubuntu4.4 Development Server<br>
+PHORONIX TEST SUITE: Phoronix Test Suite v5.4.0m1 [5313]<br>
+DOWNLOAD CACHE: 19 FILES / 2390 MB CACHE SIZE<br>
+SUPPORTED OPENBENCHMARKING.ORG REPOSITORIES:<br>
+      pts - Last Generated: 05 Oct 2014 07:16</em></p>
+<p>Phoromatic Servers are detected by the Phoronix Test Suite through Avahi or if manually configuring the Phoronix Test Suite clients to point to Phoromatic Servers. For networks without Avahi/auto-discovery support or for test systems that may be connecting from another network, the IP address and HTTP port number can be added to the local system's <em>~/.phoronix-test-suite/user-config.xml</em> with the <em>PhoromaticServers</em> element. Adding the <em>IP:port</em> (the Phoromatic Server's HTTP port) to the PhoromaticServers <em>user-config.xml</em> element for will perform targeted probing by the Phoronix Test Suite without any dependence on Avahi. Multiple Phoromatic Servers can be added if each IP:port is delimited by a comma.</p>
+<p>To connect a Phoronix Test Suite system for benchmarking to an account, log into your Phoromatic account from the web-interface and on the main/system pages will be instructions along with a specially formed string to run, e.g. <em>phoronix-test-suite phoromatic.connect 192.168.1.211:5447/I0SSJY</em>. When running that command once on the system(s) to be synced to that account, as the administrator you'll be able to validate/approve the systems from the Phoromatic web interface. After that, whenever the system(s) are to be running benchmarks, simply have the <strong>phoronix-test-suite phoromatic.connect</strong> command running on the system (after the initial account has been synced, simply running <strong>phoronix-test-suite phoromatic.connect</strong> is enough for the system to find the server and its account).</p>
+<h2>Root Administrator</h2>
+<p>The root administrator account is able to manage the server-level settings, e.g. Phoromatic storage location and other global settings related to the Phoronix Test Suite / Phoromatic Server, from the web user-interface.</p>
+<p>To enable the root administrator log-in, first from the server's command-line interface run <strong>phoronix-test-suite phoromatic.set-root-admin-password</strong> to set the password. Following that, you can log into the root administrator account via the web interface via the <em>rootadmin</em> user-name and the set password.</p>
+<h2>Other Advice</h2>
+<h3>Disable Internet Precaution</h3>
+<p>If you have an Internet connection but want to ensure your Phoronix Test Suite client doesn't attempt to use it for any matter, via the <em>~/.phoronix-test-suite/user-config.xml</em> you can set <em>NoInternetCommunication</em> to <em>TRUE</em>. There's also a NoNetworkCommunication tag, but setting that to TRUE will disable any form of network communication -- including communication with the Phoromatic Server.</p>
+<h3>Ports / Services</h3>
+<p>The Phoromatic Server process currently relies upon a PHP/HHVM built-in web server process and a PTS-hosted WebSocket server. The web server process handles the web UI and much of the responsibilities of the Phoromatic Server. Over time the PTS WebSocket server will be increasingly utilized for bi-directional, real-time communication between the server and clients -- including for features like viewing real-time hardware sensors of client systems from the server UI.</p>
+<h3>Systemd / Upstart</h3>
+<p>Packaged with the Phoronix Test Suite are basic <em>phoromatic-client</em> and <em>phoromatic-server</em> configurations for both Upstart and systemd init systems. The <em>phoromatic-server</em> configuration will launch the Phoronix Test Suite's Phoromatic Server and the <em>phoromatic-client</em> service will attempt to connect to a <u>pre-configured</u> Phoromatic Server. The systemd service files will automatically be installed via the Phoronix Test Suite <em>install-sh</em> process while the Upstart jobs can be copied from <em>deploy/phoromatic-upstart/*</em> to <em>/etc/init</em>.</p>
+<h3>Cache Verification</h3>
+<p>To confirm the files accessible to Phoronix Test Suite client systems, from the Phoromatic Server web user-interface go to the <em>settings</em> page followed by the <em>cache settings</em> link to view information about the download and OpenBenchmarking.org caches. From the client systems, running <strong>phoronix-test-suite phoromatic.explore</strong> will also supply cache statistics.</p>
+<h3>Log Files</h3>
+<p>The Phoromatic Server will produce a log file of events / debugging information to <em>~/.phoronix-test-suite/phoromatic.log</em> or <em>/var/log/phoromatic.log</em> depending upon the service's permissions. When running the Phoronix Test Suite Phoromatic client, the log will be written to one of the respective locations in <em>phoronix-test-suite.log</em>.</p>
+<h3>Multi-User Accounts</h3>
+<p>For each time a user account is made from the Phoromatic web UI's log-in page, all of the test schedules, systems, and other account information is separate to allow for a completely isolated multi-user system. If a main administrator (the one creating the account) wishes to have multiple users sharing the same account data, that user can create additional accounts from the <em>Users</em> tab of their account. The main administrator can make an additional administrator account or a "viewer" account that can consume the account's data but not create/modify the schedules, systems, or other account details.</p>
+<h3>
+<h3>File Locations</h3>
+</h3><p>When running the Phoronix Test Suite Phoromatic Server as root, rather than using the <em>~/.phoronix-test-suite/</em> directory, the standard Linux file-system hierarchy standard is honored. The main storage path is <em>/var/lib/phoronix-test-suite/</em>, the user configuration file is <em>/etc/phoronix-test-suite.xml</em>, and <em>/var/cache/phoronix-test-suite/</em> for cache files.</p>
+<h3>Uploading Other Test Results</h3>
+<p>Unscheduled test results and other results found on connected systems to a Phoromatic account can upload the data to the Phoromatic Server using the <em>phoronix-test-suite phoromatic.upload-result &lt;result file identifier &gt;</em> sub-command.</p>
+<h3>User Context File Logging</h3>
+<p>For those utilizing custom set context script files as part of the Phoromatic test schedule, any important notes / log information can be written to the file specified by the <em>PHOROMATIC_LOG_FILE</em> environment variable set while running the user context scripts. The contents of that file is then sent to the Phoromatic Server otherwise the standard output of the script's execution is submitted to the Phoromatic Server for logging. These logs can then be viewed by the Phoromatic Server along with the test results. Other environment variables accessible when running a user context script include <em>PHOROMATIC_TRIGGER</em>, <em>PHOROMATIC_SCHEDULE_ID</em>, and <em>PHOROMATIC_SCHEDULE_PROCESS</em>.</p>
 <hr style="height: 50px; border: 0;"><a name="OfflineImprovements+ConfidentialTesting/AvoidingAccidentalResultUploads"></a><h1>Offline Improvements + Confidential Testing / Avoiding Accidental Result Uploads</h1>
 <h1>Offline Enhancement Via Local Cache</h1>
 <p>Beginning with Phoronix Test Suite 9.0, there are improvements to improve the out-of-the-box experience if running the Phoronix Test Suite in a strictly offline environment / behind-the-firewall without access to OpenBenchmarking.org for being able to obtain test profiles / test suites. From Phoronix Test Suite 3.0 when OpenBenchmarking.org was introduced until Phoronix Test Suite 9.0, Internet connectivity was initially required for obtaining the test profiles/suites as the cloud/repository. OpenBenchmarking.org allows for tests to be updated independently of the Phoronix Test Suite releases as well as allowing new tests to be introduced on-demand. Aside from when new tests require explicit new PTS features, this allows tests/suites to be seamlessly used by older versions of the Phoronix Test Suite without any upgrade process required, assuming Internet connectivity is available.</p>
@@ -1336,7 +1322,7 @@ In the event that a test profile fails to install or run, the following general
 <p>If distributing a customized/local copy of the Phoronix Test Suite, the default behavior of the configuration file (in addition to deleting the pts_openbenchmarking_upload file) can be done via the user configuration defaults defined within <em>pts-core/static/user-config-defaults.xml</em>.</p>
 <hr style="height: 50px; border: 0;"><a name="DevelopmentCredits"></a><h1>Development Credits</h1>
 <p>The Phoronix Test Suite is based upon the extensive testing and internal tools developed by <a href="http://www.phoronix.com/">Phoronix.com</a> since 2004 along with support from leading tier-one computer hardware and software vendors. The principal architects of the Phoronix Test Suite are <a href="http://www.michaellarabel.com/">Michael Larabel</a> and Matthew Tippett. The phoronix-test-suite, pts_Graph, Phoromatic, Phodevi, tandem_Xml, and nye_Xml are some of the related open-source projects provided by <a href="http://www.phoronix-media.com/">Phoronix Media</a>.</p>
-<p style="padding-top: 30px; text-align: center;">Copyright &copy; 2008 - 2020 by Phoronix Media.</p></div>
+<p style="padding-top: 30px; text-align: center;">Copyright &copy; 2008 - 2021 by Phoronix Media.</p></div>
 		<div id="pts_footer">
 			<div id="pts_footer_logo"><a href="http://www.phoronix-test-suite.com/"><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" viewbox="0 0 76 41" width="76" height="41" preserveaspectratio="xMinYMin meet">
   <path d="m74 22v9m-5-16v16m-5-28v28m-23-2h12.5c2.485281 0 4.5-2.014719 4.5-4.5s-2.014719-4.5-4.5-4.5h-8c-2.485281 0-4.5-2.014719-4.5-4.5s2.014719-4.5 4.5-4.5h12.5m-21 5h-11m11 13h-2c-4.970563 0-9-4.029437-9-9v-20m-24 40v-20c0-4.970563 4.0294373-9 9-9 4.970563 0 9 4.029437 9 9s-4.029437 9-9 9h-9" stroke="#c8d905" stroke-width="4" fill="none"></path>

documentation/phoronix-test-suite.md

@@ -45,6 +45,9 @@ A simple text-driven shell interface / helper to the Phoronix Test Suite. Ideal
 #### system-info
 Display the installed system hardware and software information as detected by the Phoronix Test Suite Phodevi Library.
 
+#### system-properties
+Display various hardware/software system properties detected by the Phoronix Device Interface (Phodevi) library.
+
 #### system-sensors
 Display the installed system hardware and software sensors in real-time as detected by the Phoronix Test Suite Phodevi Library.
 
@@ -70,6 +73,9 @@ This option will permanently remove a installed test by the Phoronix Test Suite.
 #### benchmark  [Test | Suite | OpenBenchmarking ID | Test Result]  ...
 This option will install the selected test(s) (if needed) and will proceed to run the test(s). This option is equivalent to running phoronix-test-suite with the install option followed by the run option. Multiple arguments can be supplied to run additional tests at the same time and save the results into one file.
 
+#### estimate-install-time  [Test | Suite | OpenBenchmarking ID | Test Result]
+This option will provide estimates for test install/setup time length.
+
 #### estimate-run-time  [Test | Suite | OpenBenchmarking ID | Test Result]
 This option will provide estimates for test run-time / length.
 
@@ -131,6 +137,9 @@ This option and its arguments pre-set the Phoronix Test Suite batch run mode wit
 #### clone-result  [OpenBenchmarking ID]  ...
 This option will download a local copy of a file that was saved to OpenBenchmarking.org, as long as a valid public ID is supplied.
 
+#### enable-repo
+This option is used if wanting to add a new OpenBenchmarking.org account/repository to your system for enabling third-party/unofficial test profiles and test suites.
+
 #### list-recommended-tests
 This option will list recommended test profiles for benchmarking sorted by hardware sub-system. The recommended tests are determined via querying OpenBenchmarking.org and determining the most popular tests for a given environment based upon the number of times a test profile has been downloaded, the number of test results available on OpenBenchmarking.org for a given test profile, the age of the test profile, and other weighted factors.
 
@@ -166,6 +175,9 @@ This option can be used for uploading a test suite to your account on OpenBenchm
 
 
 ## Information
+#### check-tests  [Test]
+This option will perform a check on one or more test profiles to determine if there have been any vendor changes to the filename, filesize, url location, md5 and sha256 checksums.
+
 #### info  [Test | Suite | OpenBenchmarking ID | Test Result]
 This option will show details about the supplied test, suite, virtual suite, or result file.
 
@@ -217,6 +229,9 @@ This option will list all available test profiles that are available from the en
 #### search
 This option provides command-line searching abilities for test profiles / test suites / test results. The search query can be passed as a parameter otherwise the user is prompted to input their search query..
 
+#### test-to-suite-map
+This option will list all test profiles and any test suites each test belongs to.
+
 
 ## Asset Creation
 #### build-suite
@@ -243,6 +258,9 @@ This will download the selected test file(s) to the Phoronix Test Suite download
 #### inspect-test-profile  [Test]
 This option can be used for inspecting a Phoronix Test Suite test profile with providing inside details on test profiles for debugging / evaluation / learning purposes.
 
+#### rebuild-test-suite  [Suite]
+This option will regenerate the local test suite XML file against the OpenBenchmarking.org specification. This can be used to clean up any existing XML syntax / styling issues, etc.
+
 #### result-file-to-suite  [Test Result]
 This option will guide the user through the process of generating their own test suite, which they can then run, that is based upon an existing test results file.
 
@@ -275,12 +293,12 @@ This option is used if you wish to edit the title and description of an existing
 #### extract-from-result-file  [Test Result]
 This option will extract a single set of test results from a saved results file that contains multiple test results that have been merged. The user is the prompted to specify a new result file name and select which result identifier to extract.
 
+#### keep-results-in-result-file  [Test Result]
+This option is the inverse of the remove-results-from-result-file sub-command. If you wish to remove all results but those listed from a given result file, this option can be used. The user must specify a saved results file and then they will be prompted to provide a string to search for in keeping those results in that given result file but removing all other data.
+
 #### merge-results  [Test Result]  ...
 This option will manually merge multiple sets of test results generated by the Phoronix Test Suite.
 
-#### refresh-graphs  [Test Result]
-This option will re-render and save all result graphs within a saved file. This option can be used when making modifications to the graphing code or its color/option configuration file and testing the changes.
-
 #### remove-result  [Test Result]
 This option will permanently remove the saved file set that is set as the first argument.
 
@@ -320,6 +338,9 @@ This option will read a saved test results file and output the system hardware a
 #### show-result  [Test Result]
 Open up the test results in the Phoronix Test Suite Result Viewer or on OpenBenchmarking.org.
 
+#### workload-topology  [Test Result]
+This option will read a saved test results file and print the test profiles contained within and their arrangement within different test suites for getting an idea as to the workload topology/make-up / logical groupings of the benchmarks being run.
+
 
 ## Other
 #### commands
@@ -341,23 +362,6 @@ This option will display a list of available Phoronix Test Suite commands and po
 This option will display the Phoronix Test Suite client version.
 
 
-## Result Analysis
-#### analyze-all-runs  [Test Result]
-This option will generate a candlestick graph showing the distribution of results from all trial runs. The candlestick graph is similar to the Japanese candlestick charts used by the financial industry, except instead of representing stock data it is numerical result data from all trial runs.\n\nThe tip of the upper-wick represents the highest value of the test runs with the tip of the lower-wick representing the lowest value of all test runs. The upper-edge of the candle body represents the first or last run value and the lower-edge represents the first or last run value. Lastly, if the last run value is less than the first run value, the candle body is the same color as the graph background, otherwise the last run value is greater.
-
-#### executive-summary  [Test Result]
-This option will attempt to auto-generate a textual executive summary for a result file to highlight prominent results / averages.
-
-#### result-file-confidence  [Test Result]
-This option will read a saved test results file and display various statistics on the confidence of the results with the standard deviation, three-sigma values, and other metrics while color-coding "passing" results in green.
-
-#### result-file-stats  [Test Result]
-This option is used if you wish to analyze a result file by seeing various statistics on the result data for result files containing at least two sets of data.
-
-#### wins-and-losses  [Test Result]
-This option is used if you wish to analyze a result file to see which runs produced the most wins/losses of those result identifiers in the saved file.
-
-
 ## Modules
 #### auto-load-module
 This option can be used for easily adding a module to the AutoLoadModules list in the Phoronix Test Suite user configuration file. That list controls what PTS modules are automatically loaded on start-up of the Phoronix Test Suite.
@@ -395,6 +399,20 @@ This option can be used for resetting the Phoronix Test Suite user configuration
 This option can be used for setting an XML value in the Phoronix Test Suite user configuration file.
 
 
+## Result Analysis
+#### executive-summary  [Test Result]
+This option will attempt to auto-generate a textual executive summary for a result file to highlight prominent results / averages.
+
+#### result-file-confidence  [Test Result]
+This option will read a saved test results file and display various statistics on the confidence of the results with the standard deviation, three-sigma values, and other metrics while color-coding "passing" results in green.
+
+#### result-file-stats  [Test Result]
+This option is used if you wish to analyze a result file by seeing various statistics on the result data for result files containing at least two sets of data.
+
+#### wins-and-losses  [Test Result]
+This option is used if you wish to analyze a result file to see which runs produced the most wins/losses of those result identifiers in the saved file.
+
+
 ## Phoromatic
 #### start-phoromatic-server
 Start the Phoromatic web server for controlling local Phoronix Test Suite client systems to facilitate automated and repeated test orchestration and other automated features targeted at the enterprise.
@@ -433,6 +451,12 @@ Setting FLAME_GRAPH_PATH=<path to flamegraph path> will auto-load and enable thi
 This module utilizes the following environmental variables: FLAME_GRAPH_PATH.
 
 
+### Flush Caches
+Loading this module will ensure caches (page cache, swap, etc) automatically get flushed prior to running any test.
+
+This module utilizes the following environmental variables: PTS_FLUSH_CACHES.
+
+
 ### Graphics Override
 This module allows you to override some graphics rendering settings for the ATI and NVIDIA drivers while running the Phoronix Test Suite.
 
@@ -599,24 +623,19 @@ Supported Options:
   - all.hdd
   - hdd.read-speed
   - all.hdd.read-speed
-  - hdd.read-speed.sda
-  - hdd.read-speed.sdb
   - hdd.read-speed.nvme0n1
+  - hdd.read-speed.mmcblk0
   - hdd.temp
   - all.hdd.temp
-  - hdd.temp.sda
-  - hdd.temp.sdb
   - hdd.temp.nvme0n1
+  - hdd.temp.mmcblk0
   - hdd.write-speed
   - all.hdd.write-speed
-  - hdd.write-speed.sda
-  - hdd.write-speed.sdb
   - hdd.write-speed.nvme0n1
+  - hdd.write-speed.mmcblk0
   - all.memory
   - memory.temp
   - memory.usage
-  - all.network
-  - network.usage
   - all.swap
   - swap.usage
   - all.sys
@@ -630,6 +649,12 @@ Supported Options:
 NOTE: Use the "system-sensors" command to see what sensors are available for monitoring on the system.
 
 
+### Test Timeout
+This module allows killing a test if it exceeds a defined threshold, such as if the test is hung, etc. TEST_TIMEOUT_AFTER= environment variable can be used for controlling the behavior. When this variable is set, the value will can be set to "auto" or a positive integer. The value indicates the number of minutes until a test run should be aborted, such as for a safeguard against hung/deadlocked processes or other issues. Setting this to a high number as a backup would be recommended for fending off possible hangs / stalls in the testing process if the test does not quit on its own for whatever reason. If the value is "auto", it will quit if the time of a test run exceeds 3x the average time it normally takes the particular test to complete its run.
+
+This module utilizes the following environmental variables: TEST_TIMEOUT_AFTER.
+
+
 ### Timed Screenshot
 This is a module that will take a screenshot of the system at a pre-defined interval. ImageMagick must be installed onto the system prior to using this module.
 
@@ -642,6 +667,12 @@ This module toggles the system's screensaver while the Phoronix Test Suite is ru
 This module utilizes the following environmental variables: HALT_SCREENSAVER.
 
 
+### Linux Turbostat Dumper
+Setting TURBOSTAT_LOG_DIR=_DIR_ will auto-load and enable this Phoronix Test Suite module. The module will -- if turbostat is installed on the system and the user is root -- allow dumping of the TurboStat data to the specified directly on a per-test basis. This allows easily collecting of turbostat logs for each test being run.
+
+This module utilizes the following environmental variables: TURBOSTAT_LOG_DIR.
+
+
 ### Update Checker
 This module checks to see if the Phoronix Test Suite -- and its tests and suites -- are up to date plus also handles message of the day information.
 
@@ -702,7 +733,7 @@ Without all of these extensions, some capabilities of the Phoronix Test Suite wi
 ## Notes
 
 ### General
-You may need to modify the *php.ini* file on your system in order to support uploading results to OpenBenchmarking.org or logging into your OpenBenchmarking.org account. The *allow_url_fopen* , *file_uploads* , and *allow_url_include* options must be set to true in the PHP configuration. See additional information in this [Phoronix Forums support thread](http://www.phoronix.com/forums/showpost.php?p=32484&postcount=4) .
+You may need to modify the *php.ini* file on your system in order to support uploading results to OpenBenchmarking.org or logging into your OpenBenchmarking.org account. The *allow_url_fopen* , *file_uploads* , and *allow_url_include* options must be set to true in the PHP configuration.
 
 Major updates to the Phoronix Test Suite are released on a quarterly basis. The latest stable and development versions of the Phoronix Test Suite are available at [Phoronix-Test-Suite.com](http://www.phoronix-test-suite.com/) . The Git repository where the latest Phoronix Test Suite code is provided is hosted at [GitHub.com/phoronix-test-suite](https://github.com/phoronix-test-suite/phoronix-test-suite) and can be cloned/pulled from the *https://github.com/phoronix-test-suite/phoronix-test-suite.git* repository location. The latest upstream development code is housed in the master tree while older Phoronix Test Suite releases are available in their respective Git branches based upon the release's code-name.
 
@@ -737,6 +768,46 @@ The Phoronix Test Suite also supports *BSD operating systems. However, like the
 The Phoronix Test Suite is fully supported on Apple's macOS operating system. PHP ships with macOS by default so it's simply a matter of downloading the Phoronix Test Suite package, extracting it, and running the executable. For tests that rely upon a compiler, Apple's XCode with GCC and LLVM can be utilized.
 
 
+# Phoronix Test Suite On Windows
+
+### Introduction
+Phoronix Test Suite 8.0 features rewritten Windows support that is at a near feature parity to the program's long-standing support for Linux, macOS, BSD and Solaris operating systems. To make it abundantly clear, if you are using a Phoronix Test Suite version pre-8.0, you are best upgrading or ideally using Phoronix Test Suite Git as the Windows support remains in very active development at the moment as of early 2018.
+
+The Phoronix Test Suite Windows support currently targets **Windows 10 x64** and **Windows Server 2016 x64** . Earlier versions of Windows, namely Windows Server 2012 and Windows 8, may work to some extent but some hardware/software reporting features and other capabilities may be missing or report warning messages. The Phoronix Test Suite Windows support is also exclusively focused on x86 64-bit support: the Phoronix Test Suite itself will run on x86 32-bit but many of the program dependencies are configured for making use of 64-bit binaries.
+
+
+### Windows Setup / Dependencies
+As with Phoronix Test Suite on Linux and other operating systems, the principal dependency is on PHP (PHP v5.3 or newer, including PHP 7.x). Running the *phoronix-test-suite.bat* file launcher for the Phoronix Test Suite on Windows will attempt to download and setup PHP on the system under *C:\PHP* as the default location should PHP support not be found within your system's *Program Files* directories. The PHP Windows build does depend upon Microsoft Visual C++ redistributable libraries, which the Windows launcher will also attempt to download and install if needed.
+
+The Phoronix Test Suite on Windows does depend upon [Cygwin](https://www.cygwin.com/) for its Bash interpreter and other basic utilities to ease the process of porting test profiles to Windows with being able to use many of the same test installation scripts on Windows/Linux/macOS/BSD/Solaris then largely unmodified. Most of the Windows tests depend upon their respective native Windows applications/binaries while this Cygwin support is a convenience for handling these Bash setup scripts and also some test profiles that depend upon a GNU toolchain. The Phoronix Test Suite will attempt to download and setup Cygwin on the system if Cygwin isn't found in its default location of *C:\cygwin64* .
+
+Various test profiles may depend upon other "external dependencies" like Python, PERL, Steam, and Java, as examples. The Phoronix Test Suite as with its support for other operating systems and Linux distributions will attempt to install these needed dependencies on a per-test basis when needed if existing support is not detected on the system.
+
+
+### Running The Phoronix Test Suite On Windows
+The Phoronix Test Suite can run from its local directory and does not need to be "installed" to a system path or any other "setup" process prior to execution. On a clean install of Windows 10 x64 or Windows Server 2016, deploying the Phoronix Test Suite is designed to be as easy and straight-forward as possible:
+
+1. Download the Phoronix Test Suite 8.0+ or [Phoronix-Test-Suite from GitHub](https://github.com/phoronix-test-suite/phoronix-test-suite) ( [zip file](https://github.com/phoronix-test-suite/phoronix-test-suite/archive/master.zip) ).
+
+2. From the Command Prompt or PowerShell, enter the *phoronix-test-suite* directory whether it be from Git or a zipped download.
+
+3. Run the *phoronix-test-suite.bat* file that should proceed to run the Phoronix Test Suite just as you would on any other operating system. If needed the Phoronix Test Suite will try to initially download and setup PHP if needed followed by the attempted automatic Cygwin setup, etc.
+
+4. Any of the Phoronix Test Suite commands from other operating systems should work on Windows. If you are new to the Phoronix Test Suite, you may enjoy a bit more guided experience by running the **phoronix-test-suite shell** command.
+
+
+### Test Profiles On Windows
+As of March 2018, around 50 of the test profiles are currently compatible with the Phoronix Test Suite on Windows. This includes many of the popular benchmarks and other interesting test cases. Over time more test profiles will continue to be ported to Windows where applicable and there are also some Windows-only tests also supported for execution by the Phoronix Test Suite.
+
+
+### Getting Started
+Besides **phoronix-test-suite shell** and **phoronix-test-suite help** , there is also **phoronix-test-suite interactive** for helping new users understand Phoronix Test Suite benchmarking. Long story short, it should be as easy as running **phoronix-test-suite benchmark c-ray** or **phoronix-test-suite benchmark crafty** as some examples for carrying out automated, cross-platform benchmarks in a side-by-side and fully-reproducible manner.
+
+
+### Support
+Community technical support is available via [GitHub](https://github.com/phoronix-test-suite/phoronix-test-suite/issues) . For enterprise inquiries, commercial support, and custom engineering services, [contact us](http://phoronix-test-suite.com/?k=commercial) .
+
+
 # External Dependencies
 The Phoronix Test Suite has a feature known as "External Dependencies" where the Phoronix Test Suite can attempt to automatically install some of the test-specific dependencies on supported distributions. If running on a distribution where there is currently no External Dependencies profile, the needed package name(s) are listed for manual installation.
 
@@ -784,6 +855,10 @@ This is the directory where test suites are stored.
 
 
 ## Environment Variables
+**TEST_TIMEOUT_AFTER**
+
+When this variable is set, the value will can be set to *auto* or a positive integer. The value indicates the number of minutes until a test run should be aborted, such as for a safeguard against hung/deadlocked processes or other issues. Setting this to a high number as a backup would be recommended for fending off possible hangs / stalls in the testing process if the test does not quit. If the value is *auto* , it will quit if the time of a test run exceeds 3x the average time it normally takes the particular test to complete its run. In the future, auto might be enabled by default in a future PTS release.
+
 **TEST_RESULTS_NAME**
 
 When this variable is set, the value will be used as the name for automatically saving the test results.
@@ -916,6 +991,10 @@ If Phodevi fails to detect the system's monitor standard / default resolution, t
 
 To skip the Phoronix Test Suite external dependency checking/installation when installing a test, set this environment variable to *1* . If wishing to skip only certain external dependencies, set this variable's value to the name of the external dependencies (the generic dependency names used by the Phoronix Test Suite) to not install. Multiple dependencies to skip can be delimited by a comma.
 
+**PTS_EXTRA_SYSTEM_LOGS_DIR**
+
+By default the Phoronix Test Suite collects common system logs (cpuinfo, lscpu, dmesg) during the benchmarking process when saving test results. If wanting to collect additional, arbitrary system log files specific to your operating environment or for other niche system information, the *PTS_EXTRA_SYSTEM_LOGS_DIR* environment variable can be set as a path to a directory containing such log files. Prior to running the Phoronix Test Suite simply set *PTS_EXTRA_SYSTEM_LOGS_DIR* to the directory where any text files should be captured from following test completion.
+
 
 # General Information
 
@@ -926,19 +1005,17 @@ To skip the Phoronix Test Suite external dependency checking/installation when i
 
 We also try to make the Phoronix Test Suite easy-to-use by independent publications. For example, if you would like to watermark your web-site's URL into the graphs containing your test results, that can be easily modified in *~/.phoronix-test-suite/graph-config.json* . The colors and other graph settings are also stored in this XML file. If you are a publication and run into any issues with the Phoronix Test Suite or have a feature request, please let us know.
 
-A partial list of other publications using the Phoronix Test Suite can be found in [this forum thread](http://www.phoronix.com/forums/showthread.php?t=12925) .
-
 **Q: Why does the Phoronix Test Suite not use my distribution's package management system for acquiring all needed packages?**
 
 **A:** The tests themselves are generally downloaded from source and built locally on the machine, rather than fetching any distribution-specific packages. This is done to ensure more comparable results across operating systems / releases, etc. The distribution packager could be applying a number of unknown patches to the software, building the software with unique build options, or making other changes to the software that could skew the results.
 
 **Q: Besides being a developer, documentation writer, or having any other unique technical abilities, how else can I contribute to the Phoronix Test Suite?**
 
-**A:** Independent code contributions are very welcome as well as creating your own test profiles and suites. We also appreciate any feedback, comments, or other ideas either by emailing us, posting on the forums, or sending a message to the mailing list. You can also see this (outdated) [forum thread](http://www.phoronix.com/forums/showthread.php?t=16180) .
+**A:** Independent code contributions are very welcome as well as creating your own test profiles and suites. We also appreciate any feedback, comments, or other ideas either by emailing us, posting on GitHub, or sending a message to the mailing list.
 
 **Q: Do you offer technical support for the Phoronix Test Suite**
 
-**A:** Paid, professional support is available and is done via [our commercial services](http://commercial.phoronix-test-suite.com/) . We also offer Phoromatic licenses for use within a corporate intranet and other custom services. Free, community support is offered via our [mailing list](http://phoronix-test-suite.com/mailman/listinfo/trondheim-pts_phoronix-test-suite.com) , IRC channel ( *#phoronix* on *FreeNode.net* , and the [Phoronix Forums](http://www.phoronix.com/forums/) .
+**A:** Paid, professional support is available and is done via [our commercial services](http://commercial.phoronix-test-suite.com/) . We also offer Phoromatic licenses for use within a corporate intranet and other custom services. Free, community support is offered via our [mailing list](http://phoronix-test-suite.com/mailman/listinfo/trondheim-pts_phoronix-test-suite.com) , IRC channel ( *#phoronix* on *FreeNode.net* , and [GitHub](https://github.com/phoronix-test-suite) .
 
 **Q: May I put the Phoronix Test Suite logo on my company's web-site or on my product packaging?**
 
@@ -1010,69 +1087,117 @@ Virtual test suites can be installed and run just like a normal XML test suite a
 
 
 ---
-#### All PTS Tests  pts/all
-This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.
+#### All Tests In Pts  pts/all
+This is a collection of all supported test profiles found within the specified OpenBenchmarking.org repository.
+
+#### Application Tests  pts/application
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a application software test.
+
+#### Benchmark Tests  pts/benchmark
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a benchmark software test.
+
+#### BLAS (Basic Linear Algebra Sub-Routine) Tests  pts/blas
+This is a collection of test profiles having an external dependency on BLAS (Basic Linear Algebra Sub-Routine)
+
+#### C++ Boost Tests  pts/boost
+This is a collection of test profiles having an external dependency on C++ Boost
+
+#### Bsd Operating System Tests  pts/bsd
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the bsd Operating System.
+
+#### Disk Subsystem Tests  pts/disk
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the disk sub-system.
+
+#### Everything In Pts  pts/everything
+This is a collection of all test profiles found within the specified OpenBenchmarking.org repository, including unsupported tests, etc.
+
+#### Fortran Tests  pts/fortran
+This is a collection of test profiles having an external dependency on Fortran
+
+#### Game Tests  pts/game
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a game software test.
+
+#### Go Language Tests  pts/golang
+This is a collection of test profiles having an external dependency on Go Language
+
+#### Graphics Subsystem Tests  pts/graphics
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the graphics sub-system.
 
 #### Installed Tests  pts/installed
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.
 
-#### Every PTS Test  pts/everything
-This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.
+#### Java Tests  pts/java
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing java.
+
+#### LAPACK (Linear Algebra Pack) Tests  pts/lapack
+This is a collection of test profiles having an external dependency on LAPACK (Linear Algebra Pack)
 
 #### Linux Operating System Tests  pts/linux
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the linux Operating System.
 
-#### Solaris Operating System Tests  pts/solaris
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.
+#### Macosx Operating System Tests  pts/macosx
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the macosx Operating System.
 
-#### BSD Operating System Tests  pts/bsd
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.
+#### Memory Subsystem Tests  pts/memory
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the memory sub-system.
 
-#### MacOSX Operating System Tests  pts/macosx
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.
+#### Network Subsystem Tests  pts/network
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the network sub-system.
 
-#### Windows Operating System Tests  pts/windows
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.
+#### Node.js + NPM Tests  pts/node-npm
+This is a collection of test profiles having an external dependency on Node.js + NPM
 
-#### Hurd Operating System Tests  pts/hurd
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.
+#### OpenCV Tests  pts/opencv
+This is a collection of test profiles having an external dependency on OpenCV
 
-#### System Subsystem Tests  pts/system
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.
+#### Openmpi Tests  pts/openmpi
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmpi.
+
+#### Os Subsystem Tests  pts/os
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the os sub-system.
 
 #### Processor Subsystem Tests  pts/processor
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the processor sub-system.
 
-#### Graphics Subsystem Tests  pts/graphics
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.
+#### Python Tests  pts/python
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing python.
 
-#### Other Subsystem Tests  pts/other
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.
+#### Ruby Tests  pts/ruby
+This is a collection of test profiles having an external dependency on Ruby
 
-#### Utility Tests  pts/utility
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.
-
-#### Simulator Tests  pts/simulator
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.
+#### Rust Tests  pts/rust
+This is a collection of test profiles having an external dependency on Rust
 
 #### Scientific Tests  pts/scientific
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a scientific software test.
 
-#### Benchmark Tests  pts/benchmark
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.
+#### Simulator Tests  pts/simulator
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a simulator software test.
 
-#### Application Tests  pts/application
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.
+#### Solaris Operating System Tests  pts/solaris
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the solaris Operating System.
 
-#### Game Tests  pts/game
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.
+#### System Subsystem Tests  pts/system
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the system sub-system.
+
+#### Utility Tests  pts/utility
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a utility software test.
+
+#### Windows Operating System Tests  pts/windows
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the windows Operating System.
 
 #### Smp Tests  pts/smp
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.
 
+#### Opencl Tests  pts/opencl
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing opencl.
+
 #### Cuda Tests  pts/cuda
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cuda.
 
+#### Mpi Tests  pts/mpi
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing mpi.
+
 #### Openmp Tests  pts/openmp
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmp.
 
@@ -1085,6 +1210,9 @@ This is a collection of test profiles found within the specified OpenBenchmarkin
 #### Go Tests  pts/go
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing go.
 
+#### Optix Tests  pts/optix
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing optix.
+
 #### Vdpau Tests  pts/vdpau
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing vdpau.
 
@@ -1094,74 +1222,74 @@ This is a collection of test profiles found within the specified OpenBenchmarkin
 #### Responsiveness Tests  pts/responsiveness
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing responsiveness.
 
-#### Openmpi Tests  pts/openmpi
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmpi.
+#### All Tests In System  system/all
+This is a collection of all supported test profiles found within the specified OpenBenchmarking.org repository.
 
-#### All SYSTEM Tests  system/all
-This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.
+#### Application Tests  system/application
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a application software test.
+
+#### Benchmark Tests  system/benchmark
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a benchmark software test.
+
+#### BLAS (Basic Linear Algebra Sub-Routine) Tests  system/blas
+This is a collection of test profiles having an external dependency on BLAS (Basic Linear Algebra Sub-Routine)
+
+#### C++ Boost Tests  system/boost
+This is a collection of test profiles having an external dependency on C++ Boost
+
+#### Bsd Operating System Tests  system/bsd
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the bsd Operating System.
+
+#### Disk Subsystem Tests  system/disk
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the disk sub-system.
+
+#### Everything In System  system/everything
+This is a collection of all test profiles found within the specified OpenBenchmarking.org repository, including unsupported tests, etc.
+
+#### Game Tests  system/game
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a game software test.
+
+#### Graphics Subsystem Tests  system/graphics
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the graphics sub-system.
 
 #### Installed Tests  system/installed
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.
 
-#### Every SYSTEM Test  system/everything
-This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.
-
 #### Linux Operating System Tests  system/linux
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the linux Operating System.
 
-#### Solaris Operating System Tests  system/solaris
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.
-
-#### BSD Operating System Tests  system/bsd
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.
-
-#### MacOSX Operating System Tests  system/macosx
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.
-
-#### Windows Operating System Tests  system/windows
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.
-
-#### Hurd Operating System Tests  system/hurd
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.
-
-#### System Subsystem Tests  system/system
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.
-
-#### Processor Subsystem Tests  system/processor
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.
-
-#### Disk Subsystem Tests  system/disk
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Disk sub-system.
-
-#### Graphics Subsystem Tests  system/graphics
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.
-
-#### Memory Subsystem Tests  system/memory
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Memory sub-system.
+#### Macosx Operating System Tests  system/macosx
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the macosx Operating System.
 
 #### Network Subsystem Tests  system/network
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Network sub-system.
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the network sub-system.
 
-#### Other Subsystem Tests  system/other
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.
+#### OpenCV Tests  system/opencv
+This is a collection of test profiles having an external dependency on OpenCV
 
-#### Utility Tests  system/utility
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.
+#### OpenMPI Tests  system/openmpi
+This is a collection of test profiles having an external dependency on OpenMPI
 
-#### Simulator Tests  system/simulator
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.
+#### Processor Subsystem Tests  system/processor
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the processor sub-system.
+
+#### Python Tests  system/python
+This is a collection of test profiles having an external dependency on Python
 
 #### Scientific Tests  system/scientific
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a scientific software test.
 
-#### Benchmark Tests  system/benchmark
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.
+#### Solaris Operating System Tests  system/solaris
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the solaris Operating System.
 
-#### Application Tests  system/application
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.
+#### System Subsystem Tests  system/system
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the system sub-system.
 
-#### Game Tests  system/game
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.
+#### Utility Tests  system/utility
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a utility software test.
+
+#### Windows Operating System Tests  system/windows
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the windows Operating System.
 
 #### Opencl Tests  system/opencl
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing opencl.
@@ -1169,228 +1297,36 @@ This is a collection of test profiles found within the specified OpenBenchmarkin
 #### Cuda Tests  system/cuda
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cuda.
 
-#### All GIT Tests  git/all
-This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.
+#### Smp Tests  system/smp
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.
 
-#### Installed Tests  git/installed
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.
+#### All Tests In Git  git/all
+This is a collection of all supported test profiles found within the specified OpenBenchmarking.org repository.
 
-#### Every GIT Test  git/everything
-This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.
+#### Bsd Operating System Tests  git/bsd
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the bsd Operating System.
+
+#### Everything In Git  git/everything
+This is a collection of all test profiles found within the specified OpenBenchmarking.org repository, including unsupported tests, etc.
 
 #### Linux Operating System Tests  git/linux
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the linux Operating System.
 
-#### Solaris Operating System Tests  git/solaris
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.
-
-#### BSD Operating System Tests  git/bsd
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.
-
-#### MacOSX Operating System Tests  git/macosx
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.
-
-#### Windows Operating System Tests  git/windows
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.
-
-#### Hurd Operating System Tests  git/hurd
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.
-
-#### System Subsystem Tests  git/system
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.
+#### Macosx Operating System Tests  git/macosx
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the macosx Operating System.
 
 #### Processor Subsystem Tests  git/processor
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the processor sub-system.
 
-#### Disk Subsystem Tests  git/disk
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Disk sub-system.
-
-#### Graphics Subsystem Tests  git/graphics
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.
-
-#### Memory Subsystem Tests  git/memory
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Memory sub-system.
-
-#### Network Subsystem Tests  git/network
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Network sub-system.
-
-#### Other Subsystem Tests  git/other
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.
+#### Rust Tests  git/rust
+This is a collection of test profiles having an external dependency on Rust
 
 #### Utility Tests  git/utility
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.
-
-#### Simulator Tests  git/simulator
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.
-
-#### Scientific Tests  git/scientific
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.
-
-#### Benchmark Tests  git/benchmark
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.
-
-#### Application Tests  git/application
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.
-
-#### Game Tests  git/game
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.
+This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a utility software test.
 
 #### Smp Tests  git/smp
 This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.
 
-#### All PTS Tests  pts/all
-This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.
-
-#### Installed Tests  pts/installed
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.
-
-#### Every PTS Test  pts/everything
-This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.
-
-#### Linux Operating System Tests  pts/linux
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.
-
-#### Solaris Operating System Tests  pts/solaris
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.
-
-#### BSD Operating System Tests  pts/bsd
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.
-
-#### MacOSX Operating System Tests  pts/macosx
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.
-
-#### Windows Operating System Tests  pts/windows
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.
-
-#### Hurd Operating System Tests  pts/hurd
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.
-
-#### System Subsystem Tests  pts/system
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.
-
-#### Processor Subsystem Tests  pts/processor
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.
-
-#### Graphics Subsystem Tests  pts/graphics
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.
-
-#### Other Subsystem Tests  pts/other
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.
-
-#### Utility Tests  pts/utility
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.
-
-#### Simulator Tests  pts/simulator
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.
-
-#### Scientific Tests  pts/scientific
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.
-
-#### Benchmark Tests  pts/benchmark
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.
-
-#### Application Tests  pts/application
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.
-
-#### Game Tests  pts/game
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.
-
-#### Smp Tests  pts/smp
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.
-
-#### Cuda Tests  pts/cuda
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cuda.
-
-#### Openmp Tests  pts/openmp
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmp.
-
-#### Cloud Tests  pts/cloud
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cloud.
-
-#### Docker Tests  pts/docker
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing docker.
-
-#### Go Tests  pts/go
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing go.
-
-#### Vdpau Tests  pts/vdpau
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing vdpau.
-
-#### Video Tests  pts/video
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing video.
-
-#### Responsiveness Tests  pts/responsiveness
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing responsiveness.
-
-#### Openmpi Tests  pts/openmpi
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmpi.
-
-#### All WINDOWS Tests  windows/all
-This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.
-
-#### Installed Tests  windows/installed
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.
-
-#### Every WINDOWS Test  windows/everything
-This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.
-
-#### Linux Operating System Tests  windows/linux
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.
-
-#### Solaris Operating System Tests  windows/solaris
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.
-
-#### BSD Operating System Tests  windows/bsd
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.
-
-#### MacOSX Operating System Tests  windows/macosx
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.
-
-#### Windows Operating System Tests  windows/windows
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.
-
-#### Hurd Operating System Tests  windows/hurd
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.
-
-#### System Subsystem Tests  windows/system
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.
-
-#### Processor Subsystem Tests  windows/processor
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.
-
-#### Disk Subsystem Tests  windows/disk
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Disk sub-system.
-
-#### Graphics Subsystem Tests  windows/graphics
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.
-
-#### Memory Subsystem Tests  windows/memory
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Memory sub-system.
-
-#### Network Subsystem Tests  windows/network
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Network sub-system.
-
-#### Other Subsystem Tests  windows/other
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.
-
-#### Utility Tests  windows/utility
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.
-
-#### Simulator Tests  windows/simulator
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.
-
-#### Scientific Tests  windows/scientific
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.
-
-#### Benchmark Tests  windows/benchmark
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.
-
-#### Application Tests  windows/application
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.
-
-#### Game Tests  windows/game
-This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.
-
 
 # Component Testing
 
@@ -1410,10 +1346,143 @@ By default tests are installed to *~/.phoronix-test-suite/installed-tests/* . Ho
 When any disk tests are executed, the Phoronix Test Suite will attempt to log the mount options and scheduler of the disk/partition being used for testing. This information is subsequently displayed within the system information table. If the scheduler / mount options are maintained the same throughout all test runs, only a single line is displayed otherwise the options for each test run will be automatically displayed. The file-system in use is always captured and shown in the system information table.
 
 
-# Phoromatic
+# Phoronix Test Suite Phoromatic
 
-## Overview
-The Phoronix Test Suite now features its own built-in Phoromatic server and client implementations. See the *phoromatic.pdf* / *phoromatic.html* documentation for more information on this advanced capability.
+## Phoromatic Server
+
+### Introduction
+Phoromatic is a remote management system for the Phoronix Test Suite. Phoromatic allows the automatic (hence the name *Phoro-matic* ) scheduling of tests, remote installation of new tests, and the management of multiple test systems all through an intuitive, easy-to-use web interface. Tests can be scheduled to automatically run on a routine basis across multiple test systems. The test results are then available from this central, secure location.
+
+Phoromatic was originally introduced with Phoronix Test Suite 2.0 via Phoromatic.com as a project going back to 2008~2009. Phoromatic.com debuted as a hosted instance with the option of behind-the-firewall licensing for use within organizations. With Phoronix Test Suite 5.2 the model shifted to offer a local, open-source version of Phoromatic built into the Phoronix Test Suite code-base. Thanks to continued enterprise development, with Phoronix Test Suite 5.4 is now a fully-functioning, built-in version of Phoromatic that's open-source and can be used for behind-the-firewall testing without needing to push results to OpenBenchmarking.org and the ability to keep all results private.
+
+Phoromatic in Phoronix Test Suite 5.4 also has the ability to support zero-conf  network discovery using Avahi and the automatic distribution of needed test profiles/suites and test files. Phoronix Test Suite 5.4's Phoromatic is a significant breakthrough for open-source testing particularly those running this GPL benchmarking software within test labs and other large organizations.
+
+
+### Features
+Built atop the Phoronix Test Suite, Phoromatic offers many features for both enterprise and community/personal users:
+
+#### Automated Scheduling
+Whether it is every evening at 6:00PM, once every Thursday at 10:00AM or somewhere in between, Phoromatic can schedule tests to be run at user-defined intervals. The testing schedules can be updated through Phoromatic web interface. After the test(s) have run, the results will be immediately uploaded to Phoromatic.
+
+#### Extensible
+Any test profile or test suite that is compliant with the Phoronix Test Suite specification will work with Phoromatic. Phoromatic is able to leverage the hundreds of test profiles and test suites currently in the Phoronix Test Suite via OpenBenchmarking.org, along with any custom or proprietary test profiles you or your company utilize. Additionally, the Phoromatic interface allows the user to construct their own test suite(s).
+
+#### Remote Testing
+Once the test system is setup, all testing and management of that system can be done remotely. There is no need to execute Phoronix Test Suite commands locally using the GUI or command line version, but instead nearly all of the same features are accessible from the Phoromatic interface.
+
+#### Multi-System Support
+A single Phoromatic account is able to manage multiple test systems running the Phoronix Test Suite. Phoromatic supports grouping together test systems, tagging, and other features to support effectively managing many test systems. From the Phoromatic interface, installed system hardware and software from a given system can also be viewed.
+
+#### Turn-Key Deployment
+No additional software needs to be installed to support Phoromatic; all that's needed is Phoronix Test Suite 5.4 or later for full compatibility. New test systems can easily be synced with a given Phoromatic account by running a single command from the Phoronix Test Suite client.
+
+#### Result Management
+Test results are automatically uploaded to the Phoromatic account and remain private unless you opt to upload them to OpenBenchmarking.org. From the Phoromatic interface, results from multiple test systems can easily be compared and multiple results from the same systems can be used to track performance over time. There are also options to look at the statistical significance of the results and other features to efficiently and effectively analyze the system's performance.
+
+#### Decentralized
+Once the Phoronix Test Suite running on the Phoromatic Server has been able to cache all of the OpenBenchmarking.org test files and the needed files for each test, Phoromatic with any Phoronix Test Suite clients on your LAN can run fully decentralized without the need for a constant stream of OpenBenchmarking.org communication or Internet connection for that matter. (The only exception would be if your local systems don't have all their needed external dependencies and your system's package manager would need to install components like a compiler or necessary system libraries.
+
+#### Fully Open-Source
+Phoromatic is now fully open-source within the Phoronix Test Suite code-base for fostering greater development and new capabilities. Patches are welcome and Phoronix Media is available to provide commercial support and custom engineering services around Phoromatic and the Phoronix Test Suite.
+
+
+### Phoromatic Server Setup
+Phoromatic is built into the Phoronix Test Suite code-base and should be found in all packaged versions of the **phoronix-test-suite** . Starting the Phoromatic Server entails running phoronix-test-suite start-phoromatic-server after configuring the server information within *~/.phoronix-test-suite/user-config.xml* . The Phoromatic Server can with or without root permissions depending upon your firewall and the port numbers you wish to use for the server.
+
+On the "client side", any up-to-date version of the Phoronix Test Suite can automatically communicate with the Phoromatic Server. If Avahi support is available (commonly in Linux distribution repositories as _avahi-tools_ ), there should be zero-conf discovery if the Phoromatic Server and client systems are on the same LAN. If a Phoronix Test Suite client discovers a Phoromatic Server, it will attempt to use it automatically as a local download cache. In the event of no Internet connection, it will also attempt to obtain the needed OpenBenchmarking.org test/suite meta-data from the Phoromatic Server based upon its archived meta-data. This allows the Phoronix Test Suite / Phoromatic deployment on the LAN to be self-sustaining without an Internet connection as long as the systems have all installed test dependencies.
+
+Further configuration of the setup parameters for the Phoromatic Server and Phoronix Test Suite clients can be tuned via the *~/.phoronix-test-suite/user-config.xml* file. All control and configuration of the Phoromatic Server is done via the web-based interface when the Phoromatic Server is active.
+
+The Phoromatic Server utilizes PHP/HHVM's built-in web-server capabilities and there's also a Phoronix Test Suite built-in WebSocket server that's also initiated for back-end processing. At this time there are no ports set by default for these services but must be defined within the user configuration file. With the Avahi zero-conf network discovery and other automated detection in place, there's little restrictions over the port selection.
+
+Systemd and Upstart service files are shipped with the Phoronix Test Suite for those that wish to have the services automatically run as daemons. The only new requirements over the basic Phoronix Test Suite system requirements is having PHP-SQLite support installed and the newer version of PHP or HHVM is recommended for offering the best support.
+
+
+### Example Deployments
+#### Use Case A: Unrestricted Internet Access, Local Result Storage
+Systems on your network with unrestricted Internet access is the easiest and simplest deployment for the Phoronix Test Suite and Phoromatic. After installing the Phoronix Test Suite on the system you wish to designate the Phoromatic Server and have configured the *user-config.xml* file, simply run:
+
+**$ phoronix-test-suite start-phoromatic-server**
+
+Assuming you have no firewall or permission issues, the built-in web server and WebSocket server should proceed to initiate along with outputting the IP/port information for these services. Unless otherwise disabled from the user configuration file and if avahi-tools is present, the Phoromatic Server will be advertised with Avahi for zero-configuration networking.
+
+From the Phoromatic web interface you are able to create an account and from there proceed with the creating of test schedules, updating settings, and connecting systems. From the "client systems" you wish to use as the benchmarking nodes, it's simply a matter of running **phoronix-test-suite phoromatic.connect** with zero-conf networking or otherwise follow the information from the Phoromatic web interface for manual setup with the IP/port information.
+
+#### Use Case B: No Internet Available To Client Systems
+It's possible to run the Phoronix Test Suite and Phoromatic Server without a persistent Internet connection as long as you are able to first download the necessary files to the Phoromatic Server. After installing the Phoronix Test Suite on the system you wish to designate the Phoromatic Server and have configured the *user-config.xml* file, a few commands from the system while having an Internet connection will be able to cache the needed data:
+
+**$ phoronix-test-suite make-download-cache x264 xonotic ffmpeg**
+
+This command will simply download all of the needed test files for the tests/suites passed to the sub-command. Alternatively you could also pass pts/all to cache all tests. It's important though to just cache the tests/suites you'll be using on your network. This will generate the test file download cache by default to *~/.phoronix-test-suite/download-cache/* or */usr/share/phoronix-test-suite/download-cache/* depending upon your write permissions. You can always run this command later with more test files. Alternatively, if you already have a number of tests installed on the system, simply running "phoronix-test-suite make-download-cache" will generate the cache based upon the currently installed tests.
+
+**$ phoronix-test-suite make-openbenchmarking-cache**
+
+This command will cache as much of the OpenBenchmarking.org meta-data as possible for test profiles and test suites. After the above commands, the Phoromatic Server should no longer need a persistent Internet connection.
+
+**$ phoronix-test-suite start-phoromatic-server**
+
+Proceed to start the Phoromatic Server and operate as normal.
+
+For the test clients without an Internet connection, as long as they're able to reach the Phoromatic Server, the Phoromatic Server should be able to automatically serve all of the needed test files download cache and OpenBenchmarking.org meta-data to the systems locally.
+
+#### Use Case C: Phoromatic Across The Internet
+If wishing to use the same Phoromatic Server across multiple geographic locations, it's easily possible -- you just lose out on the zero-conf networking ability. To let the Phoronix Test Suite client systems know about the remote Phoromatic Server, simply add the Phoromatic Server information to the client's *PhoromaticServers* element within the *user-config.xml* . Of course, make sure the Phoromatic Server has a globally resolvable IP address and its Phoromatic HTTP/WebSocket ports are open. Once informing the client of the Phoromatic Server, the use cases as above apply in the same manner.
+
+
+### Client Setup
+From Phoronix Test Suite client systems running on the LAN, the following command will report all available detected Phoromatic Servers along with important server and debugging information:
+
+**$ phoronix-test-suite phoromatic.explore**
+
+With the following example output on finding one successful server:
+
+*IP: 192.168.1.211
+HTTP PORT: 5447
+WEBSOCKET PORT: 5427
+SERVER: PHP 5.5.9-1ubuntu4.4 Development Server
+PHORONIX TEST SUITE: Phoronix Test Suite v5.4.0m1 [5313]
+DOWNLOAD CACHE: 19 FILES / 2390 MB CACHE SIZE
+SUPPORTED OPENBENCHMARKING.ORG REPOSITORIES:
+      pts - Last Generated: 05 Oct 2014 07:16*
+
+Phoromatic Servers are detected by the Phoronix Test Suite through Avahi or if manually configuring the Phoronix Test Suite clients to point to Phoromatic Servers. For networks without Avahi/auto-discovery support or for test systems that may be connecting from another network, the IP address and HTTP port number can be added to the local system's *~/.phoronix-test-suite/user-config.xml* with the *PhoromaticServers* element. Adding the *IP:port* (the Phoromatic Server's HTTP port) to the PhoromaticServers *user-config.xml* element for will perform targeted probing by the Phoronix Test Suite without any dependence on Avahi. Multiple Phoromatic Servers can be added if each IP:port is delimited by a comma.
+
+To connect a Phoronix Test Suite system for benchmarking to an account, log into your Phoromatic account from the web-interface and on the main/system pages will be instructions along with a specially formed string to run, e.g. *phoronix-test-suite phoromatic.connect 192.168.1.211:5447/I0SSJY* . When running that command once on the system(s) to be synced to that account, as the administrator you'll be able to validate/approve the systems from the Phoromatic web interface. After that, whenever the system(s) are to be running benchmarks, simply have the **phoronix-test-suite phoromatic.connect** command running on the system (after the initial account has been synced, simply running **phoronix-test-suite phoromatic.connect** is enough for the system to find the server and its account).
+
+
+### Root Administrator
+The root administrator account is able to manage the server-level settings, e.g. Phoromatic storage location and other global settings related to the Phoronix Test Suite / Phoromatic Server, from the web user-interface.
+
+To enable the root administrator log-in, first from the server's command-line interface run **phoronix-test-suite phoromatic.set-root-admin-password** to set the password. Following that, you can log into the root administrator account via the web interface via the *rootadmin* user-name and the set password.
+
+
+### Other Advice
+#### Disable Internet Precaution
+If you have an Internet connection but want to ensure your Phoronix Test Suite client doesn't attempt to use it for any matter, via the *~/.phoronix-test-suite/user-config.xml* you can set *NoInternetCommunication* to *TRUE* . There's also a NoNetworkCommunication tag, but setting that to TRUE will disable any form of network communication -- including communication with the Phoromatic Server.
+
+#### Ports / Services
+The Phoromatic Server process currently relies upon a PHP/HHVM built-in web server process and a PTS-hosted WebSocket server. The web server process handles the web UI and much of the responsibilities of the Phoromatic Server. Over time the PTS WebSocket server will be increasingly utilized for bi-directional, real-time communication between the server and clients -- including for features like viewing real-time hardware sensors of client systems from the server UI.
+
+#### Systemd / Upstart
+Packaged with the Phoronix Test Suite are basic *phoromatic-client* and *phoromatic-server* configurations for both Upstart and systemd init systems. The *phoromatic-server* configuration will launch the Phoronix Test Suite's Phoromatic Server and the *phoromatic-client* service will attempt to connect to a _pre-configured_ Phoromatic Server. The systemd service files will automatically be installed via the Phoronix Test Suite *install-sh* process while the Upstart jobs can be copied from *deploy/phoromatic-upstart/** to */etc/init* .
+
+#### Cache Verification
+To confirm the files accessible to Phoronix Test Suite client systems, from the Phoromatic Server web user-interface go to the *settings* page followed by the *cache settings* link to view information about the download and OpenBenchmarking.org caches. From the client systems, running **phoronix-test-suite phoromatic.explore** will also supply cache statistics.
+
+#### Log Files
+The Phoromatic Server will produce a log file of events / debugging information to *~/.phoronix-test-suite/phoromatic.log* or */var/log/phoromatic.log* depending upon the service's permissions. When running the Phoronix Test Suite Phoromatic client, the log will be written to one of the respective locations in *phoronix-test-suite.log* .
+
+#### Multi-User Accounts
+For each time a user account is made from the Phoromatic web UI's log-in page, all of the test schedules, systems, and other account information is separate to allow for a completely isolated multi-user system. If a main administrator (the one creating the account) wishes to have multiple users sharing the same account data, that user can create additional accounts from the *Users* tab of their account. The main administrator can make an additional administrator account or a "viewer" account that can consume the account's data but not create/modify the schedules, systems, or other account details.
+
+#### File Locations
+When running the Phoronix Test Suite Phoromatic Server as root, rather than using the *~/.phoronix-test-suite/* directory, the standard Linux file-system hierarchy standard is honored. The main storage path is */var/lib/phoronix-test-suite/* , the user configuration file is */etc/phoronix-test-suite.xml* , and */var/cache/phoronix-test-suite/* for cache files.
+
+#### Uploading Other Test Results
+Unscheduled test results and other results found on connected systems to a Phoromatic account can upload the data to the Phoromatic Server using the *phoronix-test-suite phoromatic.upload-result <result file identifier >* sub-command.
+
+#### User Context File Logging
+For those utilizing custom set context script files as part of the Phoromatic test schedule, any important notes / log information can be written to the file specified by the *PHOROMATIC_LOG_FILE* environment variable set while running the user context scripts. The contents of that file is then sent to the Phoromatic Server otherwise the standard output of the script's execution is submitted to the Phoromatic Server for logging. These logs can then be viewed by the Phoromatic Server along with the test results. Other environment variables accessible when running a user context script include *PHOROMATIC_TRIGGER* , *PHOROMATIC_SCHEDULE_ID* , and *PHOROMATIC_SCHEDULE_PROCESS* .
 
 
 # Offline Improvements + Confidential Testing / Avoiding Accidental Result Uploads

documentation/stubs/00_user_options.html

@@ -21,6 +21,9 @@
 <h3>system-info<em>  </em>
 </h3>
 <p>Display the installed system hardware and software information as detected by the Phoronix Test Suite Phodevi Library.</p>
+<h3>system-properties<em>  </em>
+</h3>
+<p>Display various hardware/software system properties detected by the Phoronix Device Interface (Phodevi) library.</p>
 <h3>system-sensors<em>  </em>
 </h3>
 <p>Display the installed system hardware and software sensors in real-time as detected by the Phoronix Test Suite Phodevi Library.</p>
@@ -44,6 +47,9 @@
 <h3>benchmark<em>  [Test | Suite | OpenBenchmarking ID | Test Result]  ...</em>
 </h3>
 <p>This option will install the selected test(s) (if needed) and will proceed to run the test(s). This option is equivalent to running phoronix-test-suite with the install option followed by the run option. Multiple arguments can be supplied to run additional tests at the same time and save the results into one file.</p>
+<h3>estimate-install-time<em>  [Test | Suite | OpenBenchmarking ID | Test Result]</em>
+</h3>
+<p>This option will provide estimates for test install/setup time length.</p>
 <h3>estimate-run-time<em>  [Test | Suite | OpenBenchmarking ID | Test Result]</em>
 </h3>
 <p>This option will provide estimates for test run-time / length.</p>
@@ -103,6 +109,9 @@
 <h3>clone-result<em>  [OpenBenchmarking ID]  ...</em>
 </h3>
 <p>This option will download a local copy of a file that was saved to OpenBenchmarking.org, as long as a valid public ID is supplied.</p>
+<h3>enable-repo<em>  </em>
+</h3>
+<p>This option is used if wanting to add a new OpenBenchmarking.org account/repository to your system for enabling third-party/unofficial test profiles and test suites.</p>
 <h3>list-recommended-tests<em>  </em>
 </h3>
 <p>This option will list recommended test profiles for benchmarking sorted by hardware sub-system. The recommended tests are determined via querying OpenBenchmarking.org and determining the most popular tests for a given environment based upon the number of times a test profile has been downloaded, the number of test results available on OpenBenchmarking.org for a given test profile, the age of the test profile, and other weighted factors.</p>
@@ -137,6 +146,9 @@
 </h3>
 <p>This option can be used for uploading a test suite to your account on OpenBenchmarking.org. By uploading your test suite to OpenBenchmarking.org, others are then able to browse and access this test suite for easy distribution.</p>
 <h1>Information</h1>
+<h3>check-tests<em>  [Test]</em>
+</h3>
+<p>This option will perform a check on one or more test profiles to determine if there have been any vendor changes to the filename, filesize, url location, md5 and sha256 checksums.</p>
 <h3>info<em>  [Test | Suite | OpenBenchmarking ID | Test Result]</em>
 </h3>
 <p>This option will show details about the supplied test, suite, virtual suite, or result file.</p>
@@ -188,6 +200,9 @@
 <h3>search<em>  </em>
 </h3>
 <p>This option provides command-line searching abilities for test profiles / test suites / test results. The search query can be passed as a parameter otherwise the user is prompted to input their search query..</p>
+<h3>test-to-suite-map<em>  </em>
+</h3>
+<p>This option will list all test profiles and any test suites each test belongs to.</p>
 <h1>Asset Creation</h1>
 <h3>build-suite<em>  </em>
 </h3>
@@ -213,6 +228,9 @@
 <h3>inspect-test-profile<em>  [Test]</em>
 </h3>
 <p>This option can be used for inspecting a Phoronix Test Suite test profile with providing inside details on test profiles for debugging / evaluation / learning purposes.</p>
+<h3>rebuild-test-suite<em>  [Suite]</em>
+</h3>
+<p>This option will regenerate the local test suite XML file against the OpenBenchmarking.org specification. This can be used to clean up any existing XML syntax / styling issues, etc.</p>
 <h3>result-file-to-suite<em>  [Test Result]</em>
 </h3>
 <p>This option will guide the user through the process of generating their own test suite, which they can then run, that is based upon an existing test results file.</p>
@@ -244,12 +262,12 @@
 <h3>extract-from-result-file<em>  [Test Result]</em>
 </h3>
 <p>This option will extract a single set of test results from a saved results file that contains multiple test results that have been merged. The user is the prompted to specify a new result file name and select which result identifier to extract.</p>
+<h3>keep-results-in-result-file<em>  [Test Result]</em>
+</h3>
+<p>This option is the inverse of the remove-results-from-result-file sub-command. If you wish to remove all results but those listed from a given result file, this option can be used. The user must specify a saved results file and then they will be prompted to provide a string to search for in keeping those results in that given result file but removing all other data.</p>
 <h3>merge-results<em>  [Test Result]  ...</em>
 </h3>
 <p>This option will manually merge multiple sets of test results generated by the Phoronix Test Suite.</p>
-<h3>refresh-graphs<em>  [Test Result]</em>
-</h3>
-<p>This option will re-render and save all result graphs within a saved file. This option can be used when making modifications to the graphing code or its color/option configuration file and testing the changes.</p>
 <h3>remove-result<em>  [Test Result]</em>
 </h3>
 <p>This option will permanently remove the saved file set that is set as the first argument.</p>
@@ -289,6 +307,9 @@
 <h3>show-result<em>  [Test Result]</em>
 </h3>
 <p>Open up the test results in the Phoronix Test Suite Result Viewer or on OpenBenchmarking.org.</p>
+<h3>workload-topology<em>  [Test Result]</em>
+</h3>
+<p>This option will read a saved test results file and print the test profiles contained within and their arrangement within different test suites for getting an idea as to the workload topology/make-up / logical groupings of the benchmarks being run.</p>
 <h1>Other</h1>
 <h3>commands<em>  </em>
 </h3>
@@ -308,22 +329,6 @@
 <h3>version<em>  </em>
 </h3>
 <p>This option will display the Phoronix Test Suite client version.</p>
-<h1>Result Analysis</h1>
-<h3>analyze-all-runs<em>  [Test Result]</em>
-</h3>
-<p>This option will generate a candlestick graph showing the distribution of results from all trial runs. The candlestick graph is similar to the Japanese candlestick charts used by the financial industry, except instead of representing stock data it is numerical result data from all trial runs.\n\nThe tip of the upper-wick represents the highest value of the test runs with the tip of the lower-wick representing the lowest value of all test runs. The upper-edge of the candle body represents the first or last run value and the lower-edge represents the first or last run value. Lastly, if the last run value is less than the first run value, the candle body is the same color as the graph background, otherwise the last run value is greater.</p>
-<h3>executive-summary<em>  [Test Result]</em>
-</h3>
-<p>This option will attempt to auto-generate a textual executive summary for a result file to highlight prominent results / averages.</p>
-<h3>result-file-confidence<em>  [Test Result]</em>
-</h3>
-<p>This option will read a saved test results file and display various statistics on the confidence of the results with the standard deviation, three-sigma values, and other metrics while color-coding "passing" results in green.</p>
-<h3>result-file-stats<em>  [Test Result]</em>
-</h3>
-<p>This option is used if you wish to analyze a result file by seeing various statistics on the result data for result files containing at least two sets of data.</p>
-<h3>wins-and-losses<em>  [Test Result]</em>
-</h3>
-<p>This option is used if you wish to analyze a result file to see which runs produced the most wins/losses of those result identifiers in the saved file.</p>
 <h1>Modules</h1>
 <h3>auto-load-module<em>  </em>
 </h3>
@@ -359,6 +364,19 @@
 <h3>user-config-set<em>  </em>
 </h3>
 <p>This option can be used for setting an XML value in the Phoronix Test Suite user configuration file.</p>
+<h1>Result Analysis</h1>
+<h3>executive-summary<em>  [Test Result]</em>
+</h3>
+<p>This option will attempt to auto-generate a textual executive summary for a result file to highlight prominent results / averages.</p>
+<h3>result-file-confidence<em>  [Test Result]</em>
+</h3>
+<p>This option will read a saved test results file and display various statistics on the confidence of the results with the standard deviation, three-sigma values, and other metrics while color-coding "passing" results in green.</p>
+<h3>result-file-stats<em>  [Test Result]</em>
+</h3>
+<p>This option is used if you wish to analyze a result file by seeing various statistics on the result data for result files containing at least two sets of data.</p>
+<h3>wins-and-losses<em>  [Test Result]</em>
+</h3>
+<p>This option is used if you wish to analyze a result file to see which runs produced the most wins/losses of those result identifiers in the saved file.</p>
 <h1>Phoromatic</h1>
 <h3>start-phoromatic-server<em>  </em>
 </h3>

documentation/stubs/00_zmodule_options.html

@@ -16,6 +16,9 @@
 <h2>Generate Perf FlameGraphs For Tests</h2>
 <p>Setting FLAME_GRAPH_PATH=&lt;path to flamegraph path&gt; will auto-load and enable this Phoronix Test Suite module. The module will generate a Linux perf FlameGraph for each test run during the benchmarking process. Details on FlameGraph @ https://github.com/brendangregg/FlameGraph</p>
 <p>This module utilizes the following environmental variables: FLAME_GRAPH_PATH.</p>
+<h2>Flush Caches</h2>
+<p>Loading this module will ensure caches (page cache, swap, etc) automatically get flushed prior to running any test.</p>
+<p>This module utilizes the following environmental variables: PTS_FLUSH_CACHES.</p>
 <h2>Graphics Override</h2>
 <p>This module allows you to override some graphics rendering settings for the ATI and NVIDIA drivers while running the Phoronix Test Suite.</p>
 <p>This module utilizes the following environmental variables: FORCE_AA, FORCE_AF.</p>
@@ -125,24 +128,19 @@ Supported Options:
   - all.hdd
   - hdd.read-speed
   - all.hdd.read-speed
-  - hdd.read-speed.sda
-  - hdd.read-speed.sdb
   - hdd.read-speed.nvme0n1
+  - hdd.read-speed.mmcblk0
   - hdd.temp
   - all.hdd.temp
-  - hdd.temp.sda
-  - hdd.temp.sdb
   - hdd.temp.nvme0n1
+  - hdd.temp.mmcblk0
   - hdd.write-speed
   - all.hdd.write-speed
-  - hdd.write-speed.sda
-  - hdd.write-speed.sdb
   - hdd.write-speed.nvme0n1
+  - hdd.write-speed.mmcblk0
   - all.memory
   - memory.temp
   - memory.usage
-  - all.network
-  - network.usage
   - all.swap
   - swap.usage
   - all.sys
@@ -154,12 +152,18 @@ Supported Options:
   - all.sys.voltage
 
 NOTE: Use the "system-sensors" command to see what sensors are available for monitoring on the system.</p>
+<h2>Test Timeout</h2>
+<p>This module allows killing a test if it exceeds a defined threshold, such as if the test is hung, etc. TEST_TIMEOUT_AFTER= environment variable can be used for controlling the behavior. When this variable is set, the value will can be set to "auto" or a positive integer. The value indicates the number of minutes until a test run should be aborted, such as for a safeguard against hung/deadlocked processes or other issues. Setting this to a high number as a backup would be recommended for fending off possible hangs / stalls in the testing process if the test does not quit on its own for whatever reason. If the value is "auto", it will quit if the time of a test run exceeds 3x the average time it normally takes the particular test to complete its run.</p>
+<p>This module utilizes the following environmental variables: TEST_TIMEOUT_AFTER.</p>
 <h2>Timed Screenshot</h2>
 <p>This is a module that will take a screenshot of the system at a pre-defined interval. ImageMagick must be installed onto the system prior to using this module.</p>
 <p>This module utilizes the following environmental variables: SCREENSHOT_INTERVAL.</p>
 <h2>Toggle Screensaver</h2>
 <p>This module toggles the system's screensaver while the Phoronix Test Suite is running. At this time, the GNOME and KDE screensavers are supported.</p>
 <p>This module utilizes the following environmental variables: HALT_SCREENSAVER.</p>
+<h2>Linux Turbostat Dumper</h2>
+<p>Setting TURBOSTAT_LOG_DIR=_DIR_ will auto-load and enable this Phoronix Test Suite module. The module will -- if turbostat is installed on the system and the user is root -- allow dumping of the TurboStat data to the specified directly on a per-test basis. This allows easily collecting of turbostat logs for each test being run.</p>
+<p>This module utilizes the following environmental variables: TURBOSTAT_LOG_DIR.</p>
 <h2>Update Checker</h2>
 <p>This module checks to see if the Phoronix Test Suite -- and its tests and suites -- are up to date plus also handles message of the day information.</p>
 <h2>Utilize Wine On Linux Benchmarking</h2>

documentation/stubs/01_install.html

@@ -26,7 +26,7 @@
 <p>Without all of these extensions, some capabilities of the Phoronix Test Suite will not be available. Many of these packages are enabled by default and do not require any additional installation steps on most Linux distributions, otherwise they are often found in the package vendor's repository.</p>
 <h1>Notes</h1>
 <h2>General</h2>
-<p>You may need to modify the <em>php.ini</em> file on your system in order to support uploading results to OpenBenchmarking.org or logging into your OpenBenchmarking.org account. The <em>allow_url_fopen</em>, <em>file_uploads</em>, and <em>allow_url_include</em> options must be set to true in the PHP configuration. See additional information in this <a href="http://www.phoronix.com/forums/showpost.php?p=32484&amp;postcount=4">Phoronix Forums support thread</a>.</p>
+<p>You may need to modify the <em>php.ini</em> file on your system in order to support uploading results to OpenBenchmarking.org or logging into your OpenBenchmarking.org account. The <em>allow_url_fopen</em>, <em>file_uploads</em>, and <em>allow_url_include</em> options must be set to true in the PHP configuration.</p>
 <p>Major updates to the Phoronix Test Suite are released on a quarterly basis. The latest stable and development versions of the Phoronix Test Suite are available at <a href="http://www.phoronix-test-suite.com/">Phoronix-Test-Suite.com</a>. The Git repository where the latest Phoronix Test Suite code is provided is hosted at <a href="https://github.com/phoronix-test-suite/phoronix-test-suite">GitHub.com/phoronix-test-suite</a> and can be cloned/pulled from the <em>https://github.com/phoronix-test-suite/phoronix-test-suite.git</em> repository location. The latest upstream development code is housed in the master tree while older Phoronix Test Suite releases are available in their respective Git branches based upon the release's code-name.</p>
 <p>If building the PHP package from upstream sources, it should just be a matter of running <em>./configure</em> with the <em>--enable-zip</em> flag (all other requirements should be apart of the stock PHP configuration) to satisfy the PHP needs of the Phoronix Test Suite.</p>
 <h2>File Structure</h2>

documentation/stubs/01_windows.html

@@ -22,6 +22,6 @@
 <h2>Getting Started</h2>
 <p>Besides <strong>phoronix-test-suite shell</strong> and <strong>phoronix-test-suite help</strong>, there is also <strong>phoronix-test-suite interactive</strong> for helping new users understand Phoronix Test Suite benchmarking. Long story short, it should be as easy as running <strong>phoronix-test-suite benchmark c-ray</strong> or <strong>phoronix-test-suite benchmark crafty</strong> as some examples for carrying out automated, cross-platform benchmarks in a side-by-side and fully-reproducible manner.</p>
 <h2>Support</h2>
-<p>Community technical support is available via <a href="https://github.com/phoronix-test-suite/phoronix-test-suite/issues">GitHub</a> or general inquiries via <a href="https://www.phoronix.com/forums/forum/phoronix/phoronix-test-suite">the Phoronix Forums</a>. For enterprise inquiries, commercial support, and custom engineering services, <a href="http://phoronix-test-suite.com/?k=commercial">contact us</a>.</p>
+<p>Community technical support is available via <a href="https://github.com/phoronix-test-suite/phoronix-test-suite/issues">GitHub</a>. For enterprise inquiries, commercial support, and custom engineering services, <a href="http://phoronix-test-suite.com/?k=commercial">contact us</a>.</p>
 </body>
 </html>

documentation/stubs/40_configuration.html

@@ -21,6 +21,8 @@
 <p><strong>~/.phoronix-test-suite/test-suites/</strong></p>
 <p>This is the directory where test suites are stored.</p>
 <h1>Environment Variables</h1>
+<p><strong>TEST_TIMEOUT_AFTER</strong></p>
+<p>When this variable is set, the value will can be set to <em>auto</em> or a positive integer. The value indicates the number of minutes until a test run should be aborted, such as for a safeguard against hung/deadlocked processes or other issues. Setting this to a high number as a backup would be recommended for fending off possible hangs / stalls in the testing process if the test does not quit. If the value is <em>auto</em>, it will quit if the time of a test run exceeds 3x the average time it normally takes the particular test to complete its run. In the future, auto might be enabled by default in a future PTS release.</p>
 <p><strong>TEST_RESULTS_NAME</strong></p>
 <p>When this variable is set, the value will be used as the name for automatically saving the test results.</p>
 <p><strong>TEST_RESULTS_IDENTIFIER</strong></p>
@@ -87,5 +89,7 @@
 <p>If Phodevi fails to detect the system's monitor standard / default resolution, the mode can be specified in this variable. Example: <em>DEFAULT_VIDEO_MODE=1680x1050 phoronix-test-suite benchmark nexuiz</em>.</p>
 <p><strong>SKIP_EXTERNAL_DEPENDENCIES</strong></p>
 <p>To skip the Phoronix Test Suite external dependency checking/installation when installing a test, set this environment variable to <em>1</em>. If wishing to skip only certain external dependencies, set this variable's value to the name of the external dependencies (the generic dependency names used by the Phoronix Test Suite) to not install. Multiple dependencies to skip can be delimited by a comma.</p>
+<p><strong>PTS_EXTRA_SYSTEM_LOGS_DIR</strong></p>
+<p>By default the Phoronix Test Suite collects common system logs (cpuinfo, lscpu, dmesg) during the benchmarking process when saving test results. If wanting to collect additional, arbitrary system log files specific to your operating environment or for other niche system information, the <em>PTS_EXTRA_SYSTEM_LOGS_DIR</em> environment variable can be set as a path to a directory containing such log files. Prior to running the Phoronix Test Suite simply set <em>PTS_EXTRA_SYSTEM_LOGS_DIR</em> to the directory where any text files should be captured from following test completion.</p>
 </body>
 </html>

documentation/stubs/50_general_information.html

@@ -7,13 +7,12 @@
 <p><strong><em>Q:</em> May I use the Phoronix Test Suite when running benchmarks for my own publication or blog? Are there any publishing restrictions?</strong></p>
 <p><strong>A:</strong> Anyone is more than welcome to use the Phoronix Test Suite for their own publication or purpose. While the Phoronix Test Suite came out of our internal test tools for carrying out Linux hardware reviews at <a href="http://www.phoronix.com/">Phoronix.com</a>, we invite other hardware review web-sites, technology journals, and independent publications to use our software too. While not required, we would just kindly ask that you mention in your review/article that the <em>Phoronix Test Suite</em> was used for carrying out your testing, and ideally to link to <a href="http://www.phoronix-test-suite.com/">www.phoronix-test-suite.com</a> so that your readers will know where to obtain the software if they are interested in running the tests. You are also more than welcome to upload your results to <a href="http://www.openbenchmarking.org/">OpenBenchmarking.org</a> so that others may compare their results against yours in an easy manner.</p>
 <p>We also try to make the Phoronix Test Suite easy-to-use by independent publications. For example, if you would like to watermark your web-site's URL into the graphs containing your test results, that can be easily modified in <em>~/.phoronix-test-suite/graph-config.json</em>. The colors and other graph settings are also stored in this XML file. If you are a publication and run into any issues with the Phoronix Test Suite or have a feature request, please let us know.</p>
-<p>A partial list of other publications using the Phoronix Test Suite can be found in <a href="http://www.phoronix.com/forums/showthread.php?t=12925">this forum thread</a>.</p>
 <p><strong><em>Q:</em> Why does the Phoronix Test Suite not use my distribution's package management system for acquiring all needed packages?</strong></p>
 <p><strong>A:</strong> The tests themselves are generally downloaded from source and built locally on the machine, rather than fetching any distribution-specific packages. This is done to ensure more comparable results across operating systems / releases, etc. The distribution packager could be applying a number of unknown patches to the software, building the software with unique build options, or making other changes to the software that could skew the results.</p>
 <p><strong><em>Q:</em> Besides being a developer, documentation writer, or having any other unique technical abilities, how else can I contribute to the Phoronix Test Suite?</strong></p>
-<p><strong>A:</strong> Independent code contributions are very welcome as well as creating your own test profiles and suites. We also appreciate any feedback, comments, or other ideas either by emailing us, posting on the forums, or sending a message to the mailing list. You can also see this (outdated) <a href="http://www.phoronix.com/forums/showthread.php?t=16180">forum thread</a>.</p>
+<p><strong>A:</strong> Independent code contributions are very welcome as well as creating your own test profiles and suites. We also appreciate any feedback, comments, or other ideas either by emailing us, posting on GitHub, or sending a message to the mailing list.</p>
 <p><strong><em>Q:</em> Do you offer technical support for the Phoronix Test Suite</strong></p>
-<p><strong>A:</strong> Paid, professional support is available and is done via <a href="http://commercial.phoronix-test-suite.com/">our commercial services</a>. We also offer Phoromatic licenses for use within a corporate intranet and other custom services. Free, community support is offered via our <a href="http://phoronix-test-suite.com/mailman/listinfo/trondheim-pts_phoronix-test-suite.com">mailing list</a>, IRC channel (<em>#phoronix</em> on <em>FreeNode.net</em>, and the <a href="http://www.phoronix.com/forums/">Phoronix Forums</a>.</p>
+<p><strong>A:</strong> Paid, professional support is available and is done via <a href="http://commercial.phoronix-test-suite.com/">our commercial services</a>. We also offer Phoromatic licenses for use within a corporate intranet and other custom services. Free, community support is offered via our <a href="http://phoronix-test-suite.com/mailman/listinfo/trondheim-pts_phoronix-test-suite.com">mailing list</a>, IRC channel (<em>#phoronix</em> on <em>FreeNode.net</em>, and <a href="https://github.com/phoronix-test-suite">GitHub</a>.</p>
 <p><strong><em>Q:</em> May I put the Phoronix Test Suite logo on my company's web-site or on my product packaging?</strong></p>
 <p><strong>A:</strong> <a href="http://www.phoronix-test-suite.com/?k=contact">Contact us</a> for licensing information and details regarding the Phoronix Certification &amp; Qualification Suite.</p>
 <p><strong><em>Q:</em> How often is the Phoronix Test Suite updated?</strong></p>

documentation/stubs/55_virtual_suites.html

@@ -6,69 +6,117 @@
 <body>
 <p>Virtual test suites are not like a traditional test suite defined by the XML suite specification. Virtual test suites are dynamically generated in real-time by the Phoronix Test Suite client based upon the specified test critera. Virtual test suites can automatically consist of all test profiles that are compatible with a particular operating system or test profiles that meet other critera. When running a virtual suite, the OpenBenchmarking.org repository of the test profiles to use for generating the dynamic suite must be prefixed. </p>
 <p>Virtual test suites can be installed and run just like a normal XML test suite and shares nearly all of the same capabilities. However, when running a virtual suite, the user will be prompted to input any user-configuration options for needed test profiles just as they would need to do if running the test individually. When running a virtual suite, the user also has the ability to select individual tests within the suite to run or to run all of the contained test profiles. Virtual test suites are also only supported for an OpenBenchmarking.org repository if there is no test profile or test suite of the same name in the repository. Below is a list of common virtual test suites for the main Phoronix Test Suite repository, but the dynamic list of available virtual test suites based upon the enabled repositories is available by running <em>phoronix-test-suite list-available-virtual-suites.</em><hr></p>
-<h3>All PTS Tests<em>  pts/all</em>
+<h3>All Tests In Pts<em>  pts/all</em>
 </h3>
-<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.</p>
+<p>This is a collection of all supported test profiles found within the specified OpenBenchmarking.org repository.</p>
+<h3>Application Tests<em>  pts/application</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a application software test.</p>
+<h3>Benchmark Tests<em>  pts/benchmark</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a benchmark software test.</p>
+<h3>BLAS (Basic Linear Algebra Sub-Routine) Tests<em>  pts/blas</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on BLAS (Basic Linear Algebra Sub-Routine)</p>
+<h3>C++ Boost Tests<em>  pts/boost</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on C++ Boost</p>
+<h3>Bsd Operating System Tests<em>  pts/bsd</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the bsd Operating System.</p>
+<h3>Disk Subsystem Tests<em>  pts/disk</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the disk sub-system.</p>
+<h3>Everything In Pts<em>  pts/everything</em>
+</h3>
+<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository, including unsupported tests, etc.</p>
+<h3>Fortran Tests<em>  pts/fortran</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on Fortran</p>
+<h3>Game Tests<em>  pts/game</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a game software test.</p>
+<h3>Go Language Tests<em>  pts/golang</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on Go Language</p>
+<h3>Graphics Subsystem Tests<em>  pts/graphics</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the graphics sub-system.</p>
 <h3>Installed Tests<em>  pts/installed</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.</p>
-<h3>Every PTS Test<em>  pts/everything</em>
+<h3>Java Tests<em>  pts/java</em>
 </h3>
-<p>This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing java.</p>
+<h3>LAPACK (Linear Algebra Pack) Tests<em>  pts/lapack</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on LAPACK (Linear Algebra Pack)</p>
 <h3>Linux Operating System Tests<em>  pts/linux</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.</p>
-<h3>Solaris Operating System Tests<em>  pts/solaris</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the linux Operating System.</p>
+<h3>Macosx Operating System Tests<em>  pts/macosx</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.</p>
-<h3>BSD Operating System Tests<em>  pts/bsd</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the macosx Operating System.</p>
+<h3>Memory Subsystem Tests<em>  pts/memory</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.</p>
-<h3>MacOSX Operating System Tests<em>  pts/macosx</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the memory sub-system.</p>
+<h3>Network Subsystem Tests<em>  pts/network</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.</p>
-<h3>Windows Operating System Tests<em>  pts/windows</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the network sub-system.</p>
+<h3>Node.js + NPM Tests<em>  pts/node-npm</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.</p>
-<h3>Hurd Operating System Tests<em>  pts/hurd</em>
+<p>This is a collection of test profiles having an external dependency on Node.js + NPM</p>
+<h3>OpenCV Tests<em>  pts/opencv</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.</p>
-<h3>System Subsystem Tests<em>  pts/system</em>
+<p>This is a collection of test profiles having an external dependency on OpenCV</p>
+<h3>Openmpi Tests<em>  pts/openmpi</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmpi.</p>
+<h3>Os Subsystem Tests<em>  pts/os</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the os sub-system.</p>
 <h3>Processor Subsystem Tests<em>  pts/processor</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.</p>
-<h3>Graphics Subsystem Tests<em>  pts/graphics</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the processor sub-system.</p>
+<h3>Python Tests<em>  pts/python</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.</p>
-<h3>Other Subsystem Tests<em>  pts/other</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing python.</p>
+<h3>Ruby Tests<em>  pts/ruby</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.</p>
-<h3>Utility Tests<em>  pts/utility</em>
+<p>This is a collection of test profiles having an external dependency on Ruby</p>
+<h3>Rust Tests<em>  pts/rust</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.</p>
-<h3>Simulator Tests<em>  pts/simulator</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.</p>
+<p>This is a collection of test profiles having an external dependency on Rust</p>
 <h3>Scientific Tests<em>  pts/scientific</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.</p>
-<h3>Benchmark Tests<em>  pts/benchmark</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a scientific software test.</p>
+<h3>Simulator Tests<em>  pts/simulator</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.</p>
-<h3>Application Tests<em>  pts/application</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a simulator software test.</p>
+<h3>Solaris Operating System Tests<em>  pts/solaris</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.</p>
-<h3>Game Tests<em>  pts/game</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the solaris Operating System.</p>
+<h3>System Subsystem Tests<em>  pts/system</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the system sub-system.</p>
+<h3>Utility Tests<em>  pts/utility</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a utility software test.</p>
+<h3>Windows Operating System Tests<em>  pts/windows</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the windows Operating System.</p>
 <h3>Smp Tests<em>  pts/smp</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.</p>
+<h3>Opencl Tests<em>  pts/opencl</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing opencl.</p>
 <h3>Cuda Tests<em>  pts/cuda</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cuda.</p>
+<h3>Mpi Tests<em>  pts/mpi</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing mpi.</p>
 <h3>Openmp Tests<em>  pts/openmp</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmp.</p>
@@ -81,6 +129,9 @@
 <h3>Go Tests<em>  pts/go</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing go.</p>
+<h3>Optix Tests<em>  pts/optix</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing optix.</p>
 <h3>Vdpau Tests<em>  pts/vdpau</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing vdpau.</p>
@@ -90,302 +141,110 @@
 <h3>Responsiveness Tests<em>  pts/responsiveness</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing responsiveness.</p>
-<h3>Openmpi Tests<em>  pts/openmpi</em>
+<h3>All Tests In System<em>  system/all</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmpi.</p>
-<h3>All SYSTEM Tests<em>  system/all</em>
+<p>This is a collection of all supported test profiles found within the specified OpenBenchmarking.org repository.</p>
+<h3>Application Tests<em>  system/application</em>
 </h3>
-<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a application software test.</p>
+<h3>Benchmark Tests<em>  system/benchmark</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a benchmark software test.</p>
+<h3>BLAS (Basic Linear Algebra Sub-Routine) Tests<em>  system/blas</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on BLAS (Basic Linear Algebra Sub-Routine)</p>
+<h3>C++ Boost Tests<em>  system/boost</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on C++ Boost</p>
+<h3>Bsd Operating System Tests<em>  system/bsd</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the bsd Operating System.</p>
+<h3>Disk Subsystem Tests<em>  system/disk</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the disk sub-system.</p>
+<h3>Everything In System<em>  system/everything</em>
+</h3>
+<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository, including unsupported tests, etc.</p>
+<h3>Game Tests<em>  system/game</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a game software test.</p>
+<h3>Graphics Subsystem Tests<em>  system/graphics</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the graphics sub-system.</p>
 <h3>Installed Tests<em>  system/installed</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.</p>
-<h3>Every SYSTEM Test<em>  system/everything</em>
-</h3>
-<p>This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.</p>
 <h3>Linux Operating System Tests<em>  system/linux</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.</p>
-<h3>Solaris Operating System Tests<em>  system/solaris</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the linux Operating System.</p>
+<h3>Macosx Operating System Tests<em>  system/macosx</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.</p>
-<h3>BSD Operating System Tests<em>  system/bsd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.</p>
-<h3>MacOSX Operating System Tests<em>  system/macosx</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.</p>
-<h3>Windows Operating System Tests<em>  system/windows</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.</p>
-<h3>Hurd Operating System Tests<em>  system/hurd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.</p>
-<h3>System Subsystem Tests<em>  system/system</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.</p>
-<h3>Processor Subsystem Tests<em>  system/processor</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.</p>
-<h3>Disk Subsystem Tests<em>  system/disk</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Disk sub-system.</p>
-<h3>Graphics Subsystem Tests<em>  system/graphics</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.</p>
-<h3>Memory Subsystem Tests<em>  system/memory</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Memory sub-system.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the macosx Operating System.</p>
 <h3>Network Subsystem Tests<em>  system/network</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Network sub-system.</p>
-<h3>Other Subsystem Tests<em>  system/other</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the network sub-system.</p>
+<h3>OpenCV Tests<em>  system/opencv</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.</p>
-<h3>Utility Tests<em>  system/utility</em>
+<p>This is a collection of test profiles having an external dependency on OpenCV</p>
+<h3>OpenMPI Tests<em>  system/openmpi</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.</p>
-<h3>Simulator Tests<em>  system/simulator</em>
+<p>This is a collection of test profiles having an external dependency on OpenMPI</p>
+<h3>Processor Subsystem Tests<em>  system/processor</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the processor sub-system.</p>
+<h3>Python Tests<em>  system/python</em>
+</h3>
+<p>This is a collection of test profiles having an external dependency on Python</p>
 <h3>Scientific Tests<em>  system/scientific</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.</p>
-<h3>Benchmark Tests<em>  system/benchmark</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a scientific software test.</p>
+<h3>Solaris Operating System Tests<em>  system/solaris</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.</p>
-<h3>Application Tests<em>  system/application</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the solaris Operating System.</p>
+<h3>System Subsystem Tests<em>  system/system</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.</p>
-<h3>Game Tests<em>  system/game</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the system sub-system.</p>
+<h3>Utility Tests<em>  system/utility</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a utility software test.</p>
+<h3>Windows Operating System Tests<em>  system/windows</em>
+</h3>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the windows Operating System.</p>
 <h3>Opencl Tests<em>  system/opencl</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing opencl.</p>
 <h3>Cuda Tests<em>  system/cuda</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cuda.</p>
-<h3>All GIT Tests<em>  git/all</em>
+<h3>Smp Tests<em>  system/smp</em>
 </h3>
-<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.</p>
-<h3>Installed Tests<em>  git/installed</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.</p>
+<h3>All Tests In Git<em>  git/all</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.</p>
-<h3>Every GIT Test<em>  git/everything</em>
+<p>This is a collection of all supported test profiles found within the specified OpenBenchmarking.org repository.</p>
+<h3>Bsd Operating System Tests<em>  git/bsd</em>
 </h3>
-<p>This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the bsd Operating System.</p>
+<h3>Everything In Git<em>  git/everything</em>
+</h3>
+<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository, including unsupported tests, etc.</p>
 <h3>Linux Operating System Tests<em>  git/linux</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.</p>
-<h3>Solaris Operating System Tests<em>  git/solaris</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the linux Operating System.</p>
+<h3>Macosx Operating System Tests<em>  git/macosx</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.</p>
-<h3>BSD Operating System Tests<em>  git/bsd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.</p>
-<h3>MacOSX Operating System Tests<em>  git/macosx</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.</p>
-<h3>Windows Operating System Tests<em>  git/windows</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.</p>
-<h3>Hurd Operating System Tests<em>  git/hurd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.</p>
-<h3>System Subsystem Tests<em>  git/system</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the macosx Operating System.</p>
 <h3>Processor Subsystem Tests<em>  git/processor</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.</p>
-<h3>Disk Subsystem Tests<em>  git/disk</em>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the processor sub-system.</p>
+<h3>Rust Tests<em>  git/rust</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Disk sub-system.</p>
-<h3>Graphics Subsystem Tests<em>  git/graphics</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.</p>
-<h3>Memory Subsystem Tests<em>  git/memory</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Memory sub-system.</p>
-<h3>Network Subsystem Tests<em>  git/network</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Network sub-system.</p>
-<h3>Other Subsystem Tests<em>  git/other</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.</p>
+<p>This is a collection of test profiles having an external dependency on Rust</p>
 <h3>Utility Tests<em>  git/utility</em>
 </h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.</p>
-<h3>Simulator Tests<em>  git/simulator</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.</p>
-<h3>Scientific Tests<em>  git/scientific</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.</p>
-<h3>Benchmark Tests<em>  git/benchmark</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.</p>
-<h3>Application Tests<em>  git/application</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.</p>
-<h3>Game Tests<em>  git/game</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.</p>
+<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a utility software test.</p>
 <h3>Smp Tests<em>  git/smp</em>
 </h3>
 <p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.</p>
-<h3>All PTS Tests<em>  pts/all</em>
-</h3>
-<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.</p>
-<h3>Installed Tests<em>  pts/installed</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.</p>
-<h3>Every PTS Test<em>  pts/everything</em>
-</h3>
-<p>This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.</p>
-<h3>Linux Operating System Tests<em>  pts/linux</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.</p>
-<h3>Solaris Operating System Tests<em>  pts/solaris</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.</p>
-<h3>BSD Operating System Tests<em>  pts/bsd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.</p>
-<h3>MacOSX Operating System Tests<em>  pts/macosx</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.</p>
-<h3>Windows Operating System Tests<em>  pts/windows</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.</p>
-<h3>Hurd Operating System Tests<em>  pts/hurd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.</p>
-<h3>System Subsystem Tests<em>  pts/system</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.</p>
-<h3>Processor Subsystem Tests<em>  pts/processor</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.</p>
-<h3>Graphics Subsystem Tests<em>  pts/graphics</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.</p>
-<h3>Other Subsystem Tests<em>  pts/other</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.</p>
-<h3>Utility Tests<em>  pts/utility</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.</p>
-<h3>Simulator Tests<em>  pts/simulator</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.</p>
-<h3>Scientific Tests<em>  pts/scientific</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.</p>
-<h3>Benchmark Tests<em>  pts/benchmark</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.</p>
-<h3>Application Tests<em>  pts/application</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.</p>
-<h3>Game Tests<em>  pts/game</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.</p>
-<h3>Smp Tests<em>  pts/smp</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing smp.</p>
-<h3>Cuda Tests<em>  pts/cuda</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cuda.</p>
-<h3>Openmp Tests<em>  pts/openmp</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmp.</p>
-<h3>Cloud Tests<em>  pts/cloud</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing cloud.</p>
-<h3>Docker Tests<em>  pts/docker</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing docker.</p>
-<h3>Go Tests<em>  pts/go</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing go.</p>
-<h3>Vdpau Tests<em>  pts/vdpau</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing vdpau.</p>
-<h3>Video Tests<em>  pts/video</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing video.</p>
-<h3>Responsiveness Tests<em>  pts/responsiveness</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing responsiveness.</p>
-<h3>Openmpi Tests<em>  pts/openmpi</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified via an internal tag as testing openmpi.</p>
-<h3>All WINDOWS Tests<em>  windows/all</em>
-</h3>
-<p>This is a collection of all test profiles found within the specified OpenBenchmarking.org repository.</p>
-<h3>Installed Tests<em>  windows/installed</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository that are already installed on the system under test.</p>
-<h3>Every WINDOWS Test<em>  windows/everything</em>
-</h3>
-<p>This is a collection of every test profile found within the specified OpenBenchmarking.org repository, including unsupported tests.</p>
-<h3>Linux Operating System Tests<em>  windows/linux</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Linux Operating System.</p>
-<h3>Solaris Operating System Tests<em>  windows/solaris</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Solaris Operating System.</p>
-<h3>BSD Operating System Tests<em>  windows/bsd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the BSD Operating System.</p>
-<h3>MacOSX Operating System Tests<em>  windows/macosx</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the MacOSX Operating System.</p>
-<h3>Windows Operating System Tests<em>  windows/windows</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Windows Operating System.</p>
-<h3>Hurd Operating System Tests<em>  windows/hurd</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being compatible with the Hurd Operating System.</p>
-<h3>System Subsystem Tests<em>  windows/system</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the System sub-system.</p>
-<h3>Processor Subsystem Tests<em>  windows/processor</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Processor sub-system.</p>
-<h3>Disk Subsystem Tests<em>  windows/disk</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Disk sub-system.</p>
-<h3>Graphics Subsystem Tests<em>  windows/graphics</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Graphics sub-system.</p>
-<h3>Memory Subsystem Tests<em>  windows/memory</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Memory sub-system.</p>
-<h3>Network Subsystem Tests<em>  windows/network</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Network sub-system.</p>
-<h3>Other Subsystem Tests<em>  windows/other</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a test of the Other sub-system.</p>
-<h3>Utility Tests<em>  windows/utility</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Utility software test.</p>
-<h3>Simulator Tests<em>  windows/simulator</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Simulator software test.</p>
-<h3>Scientific Tests<em>  windows/scientific</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Scientific software test.</p>
-<h3>Benchmark Tests<em>  windows/benchmark</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Benchmark software test.</p>
-<h3>Application Tests<em>  windows/application</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Application software test.</p>
-<h3>Game Tests<em>  windows/game</em>
-</h3>
-<p>This is a collection of test profiles found within the specified OpenBenchmarking.org repository where the test profile is specified as being a Game software test.</p>
 </body>
 </html>

documentation/stubs/60_phoromatic.html

@@ -1,9 +1,90 @@
-<html>
+<html xmlns="http://www.w3.org/1999/xhtml">
 <head>
-<Title>Phoromatic</Title>
+<Title>Phoronix Test Suite Phoromatic</Title>
 </head>
 <body>
-<h1>Overview</h1>
-<p>The Phoronix Test Suite now features its own built-in Phoromatic server and client implementations. See the <em>phoromatic.pdf</em> / <em>phoromatic.html</em> documentation for more information on this advanced capability.</p>
+<h1>Phoromatic Server</h1>
+<h2>Introduction</h2>
+<p>Phoromatic is a remote management system for the Phoronix Test Suite. Phoromatic allows the automatic (hence the name <em>Phoro-matic</em>) scheduling of tests, remote installation of new tests, and the management of multiple test systems all through an intuitive, easy-to-use web interface. Tests can be scheduled to automatically run on a routine basis across multiple test systems. The test results are then available from this central, secure location.</p>
+<p>Phoromatic was originally introduced with Phoronix Test Suite 2.0 via Phoromatic.com as a project going back to 2008~2009. Phoromatic.com debuted as a hosted instance with the option of behind-the-firewall licensing for use within organizations. With Phoronix Test Suite 5.2 the model shifted to offer a local, open-source version of Phoromatic built into the Phoronix Test Suite code-base. Thanks to continued enterprise development, with Phoronix Test Suite 5.4 is now a fully-functioning, built-in version of Phoromatic that's open-source and can be used for behind-the-firewall testing without needing to push results to OpenBenchmarking.org and the ability to keep all results private.</p>
+<p>Phoromatic in Phoronix Test Suite 5.4 also has the ability to support zero-conf  network discovery using Avahi and the automatic distribution of needed test profiles/suites and test files. Phoronix Test Suite 5.4's Phoromatic is a significant breakthrough for open-source testing particularly those running this GPL benchmarking software within test labs and other large organizations.</p>
+<h2>Features</h2>
+<p>Built atop the Phoronix Test Suite, Phoromatic offers many features for both enterprise and community/personal users:</p>
+<h3>Automated Scheduling</h3>
+<p>Whether it is every evening at 6:00PM, once every Thursday at 10:00AM or somewhere in between, Phoromatic can schedule tests to be run at user-defined intervals. The testing schedules can be updated through Phoromatic web interface. After the test(s) have run, the results will be immediately uploaded to Phoromatic.</p>
+<h3>Extensible</h3>
+<p>Any test profile or test suite that is compliant with the Phoronix Test Suite specification will work with Phoromatic. Phoromatic is able to leverage the hundreds of test profiles and test suites currently in the Phoronix Test Suite via OpenBenchmarking.org, along with any custom or proprietary test profiles you or your company utilize. Additionally, the Phoromatic interface allows the user to construct their own test suite(s).</p>
+<h3>Remote Testing</h3>
+<p>Once the test system is setup, all testing and management of that system can be done remotely. There is no need to execute Phoronix Test Suite commands locally using the GUI or command line version, but instead nearly all of the same features are accessible from the Phoromatic interface.</p>
+<h3>Multi-System Support</h3>
+<p>A single Phoromatic account is able to manage multiple test systems running the Phoronix Test Suite. Phoromatic supports grouping together test systems, tagging, and other features to support effectively managing many test systems. From the Phoromatic interface, installed system hardware and software from a given system can also be viewed.</p>
+<h3>Turn-Key Deployment</h3>
+<p>No additional software needs to be installed to support Phoromatic; all that's needed is Phoronix Test Suite 5.4 or later for full compatibility. New test systems can easily be synced with a given Phoromatic account by running a single command from the Phoronix Test Suite client.</p>
+<h3>Result Management</h3>
+<p>Test results are automatically uploaded to the Phoromatic account and remain private unless you opt to upload them to OpenBenchmarking.org. From the Phoromatic interface, results from multiple test systems can easily be compared and multiple results from the same systems can be used to track performance over time. There are also options to look at the statistical significance of the results and other features to efficiently and effectively analyze the system's performance.</p>
+<h3>Decentralized</h3>
+<p>Once the Phoronix Test Suite running on the Phoromatic Server has been able to cache all of the OpenBenchmarking.org test files and the needed files for each test, Phoromatic with any Phoronix Test Suite clients on your LAN can run fully decentralized without the need for a constant stream of OpenBenchmarking.org communication or Internet connection for that matter. (The only exception would be if your local systems don't have all their needed external dependencies and your system's package manager would need to install components like a compiler or necessary system libraries.</p>
+<h3>Fully Open-Source</h3>
+<p>Phoromatic is now fully open-source within the Phoronix Test Suite code-base for fostering greater development and new capabilities. Patches are welcome and Phoronix Media is available to provide commercial support and custom engineering services around Phoromatic and the Phoronix Test Suite.</p>
+<h2>Phoromatic Server Setup</h2>
+<p>Phoromatic is built into the Phoronix Test Suite code-base and should be found in all packaged versions of the <strong>phoronix-test-suite</strong>. Starting the Phoromatic Server entails running phoronix-test-suite start-phoromatic-server after configuring the server information within <em>~/.phoronix-test-suite/user-config.xml</em>. The Phoromatic Server can with or without root permissions depending upon your firewall and the port numbers you wish to use for the server.</p>
+<p>On the "client side", any up-to-date version of the Phoronix Test Suite can automatically communicate with the Phoromatic Server. If Avahi support is available (commonly in Linux distribution repositories as <u>avahi-tools</u>), there should be zero-conf discovery if the Phoromatic Server and client systems are on the same LAN. If a Phoronix Test Suite client discovers a Phoromatic Server, it will attempt to use it automatically as a local download cache. In the event of no Internet connection, it will also attempt to obtain the needed OpenBenchmarking.org test/suite meta-data from the Phoromatic Server based upon its archived meta-data. This allows the Phoronix Test Suite / Phoromatic deployment on the LAN to be self-sustaining without an Internet connection as long as the systems have all installed test dependencies.</p>
+<p>Further configuration of the setup parameters for the Phoromatic Server and Phoronix Test Suite clients can be tuned via the <em>~/.phoronix-test-suite/user-config.xml</em> file. All control and configuration of the Phoromatic Server is done via the web-based interface when the Phoromatic Server is active.</p>
+<p>The Phoromatic Server utilizes PHP/HHVM's built-in web-server capabilities and there's also a Phoronix Test Suite built-in WebSocket server that's also initiated for back-end processing. At this time there are no ports set by default for these services but must be defined within the user configuration file. With the Avahi zero-conf network discovery and other automated detection in place, there's little restrictions over the port selection.</p>
+<p>Systemd and Upstart service files are shipped with the Phoronix Test Suite for those that wish to have the services automatically run as daemons. The only new requirements over the basic Phoronix Test Suite system requirements is having PHP-SQLite support installed and the newer version of PHP or HHVM is recommended for offering the best support.</p>
+<h2>Example Deployments</h2>
+<h3>Use Case A: Unrestricted Internet Access, Local Result Storage</h3>
+<p>Systems on your network with unrestricted Internet access is the easiest and simplest deployment for the Phoronix Test Suite and Phoromatic. After installing the Phoronix Test Suite on the system you wish to designate the Phoromatic Server and have configured the <em>user-config.xml</em> file, simply run:</p>
+<p><strong>$ phoronix-test-suite start-phoromatic-server</strong></p>
+<p>Assuming you have no firewall or permission issues, the built-in web server and WebSocket server should proceed to initiate along with outputting the IP/port information for these services. Unless otherwise disabled from the user configuration file and if avahi-tools is present, the Phoromatic Server will be advertised with Avahi for zero-configuration networking.</p>
+<p>From the Phoromatic web interface you are able to create an account and from there proceed with the creating of test schedules, updating settings, and connecting systems. From the "client systems" you wish to use as the benchmarking nodes, it's simply a matter of running <strong>phoronix-test-suite phoromatic.connect</strong> with zero-conf networking or otherwise follow the information from the Phoromatic web interface for manual setup with the IP/port information.</p>
+<h3>Use Case B: No Internet Available To Client Systems</h3>
+<p>It's possible to run the Phoronix Test Suite and Phoromatic Server without a persistent Internet connection as long as you are able to first download the necessary files to the Phoromatic Server. After installing the Phoronix Test Suite on the system you wish to designate the Phoromatic Server and have configured the <em>user-config.xml</em> file, a few commands from the system while having an Internet connection will be able to cache the needed data:</p>
+<p><strong>$ phoronix-test-suite make-download-cache x264 xonotic ffmpeg</strong></p>
+<p>This command will simply download all of the needed test files for the tests/suites passed to the sub-command. Alternatively you could also pass pts/all to cache all tests. It's important though to just cache the tests/suites you'll be using on your network. This will generate the test file download cache by default to <em>~/.phoronix-test-suite/download-cache/</em> or <em>/usr/share/phoronix-test-suite/download-cache/</em> depending upon your write permissions. You can always run this command later with more test files. Alternatively, if you already have a number of tests installed on the system, simply running "phoronix-test-suite make-download-cache" will generate the cache based upon the currently installed tests.</p>
+<p><strong>$ phoronix-test-suite make-openbenchmarking-cache</strong></p>
+<p>This command will cache as much of the OpenBenchmarking.org meta-data as possible for test profiles and test suites. After the above commands, the Phoromatic Server should no longer need a persistent Internet connection.</p>
+<p><strong>$ phoronix-test-suite start-phoromatic-server</strong></p>
+<p>Proceed to start the Phoromatic Server and operate as normal.</p>
+<p>For the test clients without an Internet connection, as long as they're able to reach the Phoromatic Server, the Phoromatic Server should be able to automatically serve all of the needed test files download cache and OpenBenchmarking.org meta-data to the systems locally.</p>
+<h3>Use Case C: Phoromatic Across The Internet</h3>
+<p>If wishing to use the same Phoromatic Server across multiple geographic locations, it's easily possible -- you just lose out on the zero-conf networking ability. To let the Phoronix Test Suite client systems know about the remote Phoromatic Server, simply add the Phoromatic Server information to the client's <em>PhoromaticServers</em> element within the <em>user-config.xml</em>. Of course, make sure the Phoromatic Server has a globally resolvable IP address and its Phoromatic HTTP/WebSocket ports are open. Once informing the client of the Phoromatic Server, the use cases as above apply in the same manner.</p>
+<h2>Client Setup</h2>
+<p>From Phoronix Test Suite client systems running on the LAN, the following command will report all available detected Phoromatic Servers along with important server and debugging information:</p>
+<p><strong>$ phoronix-test-suite phoromatic.explore</strong></p>
+<p>With the following example output on finding one successful server:</p>
+<p><em>IP: 192.168.1.211<br />
+HTTP PORT: 5447<br />
+WEBSOCKET PORT: 5427<br />
+SERVER: PHP 5.5.9-1ubuntu4.4 Development Server<br />
+PHORONIX TEST SUITE: Phoronix Test Suite v5.4.0m1 [5313]<br />
+DOWNLOAD CACHE: 19 FILES / 2390 MB CACHE SIZE<br />
+SUPPORTED OPENBENCHMARKING.ORG REPOSITORIES:<br />
+      pts - Last Generated: 05 Oct 2014 07:16</em></p>
+<p>Phoromatic Servers are detected by the Phoronix Test Suite through Avahi or if manually configuring the Phoronix Test Suite clients to point to Phoromatic Servers. For networks without Avahi/auto-discovery support or for test systems that may be connecting from another network, the IP address and HTTP port number can be added to the local system's <em>~/.phoronix-test-suite/user-config.xml</em> with the <em>PhoromaticServers</em> element. Adding the <em>IP:port</em> (the Phoromatic Server's HTTP port) to the PhoromaticServers <em>user-config.xml</em> element for will perform targeted probing by the Phoronix Test Suite without any dependence on Avahi. Multiple Phoromatic Servers can be added if each IP:port is delimited by a comma.</p>
+<p>To connect a Phoronix Test Suite system for benchmarking to an account, log into your Phoromatic account from the web-interface and on the main/system pages will be instructions along with a specially formed string to run, e.g. <em>phoronix-test-suite phoromatic.connect 192.168.1.211:5447/I0SSJY</em>. When running that command once on the system(s) to be synced to that account, as the administrator you'll be able to validate/approve the systems from the Phoromatic web interface. After that, whenever the system(s) are to be running benchmarks, simply have the <strong>phoronix-test-suite phoromatic.connect</strong> command running on the system (after the initial account has been synced, simply running <strong>phoronix-test-suite phoromatic.connect</strong> is enough for the system to find the server and its account).</p>
+<h2>Root Administrator</h2>
+<p>The root administrator account is able to manage the server-level settings, e.g. Phoromatic storage location and other global settings related to the Phoronix Test Suite / Phoromatic Server, from the web user-interface.</p>
+<p>To enable the root administrator log-in, first from the server's command-line interface run <strong>phoronix-test-suite phoromatic.set-root-admin-password</strong> to set the password. Following that, you can log into the root administrator account via the web interface via the <em>rootadmin</em> user-name and the set password.</p>
+<h2>Other Advice</h2>
+<h3>Disable Internet Precaution</h3>
+<p>If you have an Internet connection but want to ensure your Phoronix Test Suite client doesn't attempt to use it for any matter, via the <em>~/.phoronix-test-suite/user-config.xml</em> you can set <em>NoInternetCommunication</em> to <em>TRUE</em>. There's also a NoNetworkCommunication tag, but setting that to TRUE will disable any form of network communication -- including communication with the Phoromatic Server.</p>
+<h3>Ports / Services</h3>
+<p>The Phoromatic Server process currently relies upon a PHP/HHVM built-in web server process and a PTS-hosted WebSocket server. The web server process handles the web UI and much of the responsibilities of the Phoromatic Server. Over time the PTS WebSocket server will be increasingly utilized for bi-directional, real-time communication between the server and clients -- including for features like viewing real-time hardware sensors of client systems from the server UI.</p>
+<h3>Systemd / Upstart</h3>
+<p>Packaged with the Phoronix Test Suite are basic <em>phoromatic-client</em> and <em>phoromatic-server</em> configurations for both Upstart and systemd init systems. The <em>phoromatic-server</em> configuration will launch the Phoronix Test Suite's Phoromatic Server and the <em>phoromatic-client</em> service will attempt to connect to a <u>pre-configured</u> Phoromatic Server. The systemd service files will automatically be installed via the Phoronix Test Suite <em>install-sh</em> process while the Upstart jobs can be copied from <em>deploy/phoromatic-upstart/*</em> to <em>/etc/init</em>.</p>
+<h3>Cache Verification</h3>
+<p>To confirm the files accessible to Phoronix Test Suite client systems, from the Phoromatic Server web user-interface go to the <em>settings</em> page followed by the <em>cache settings</em> link to view information about the download and OpenBenchmarking.org caches. From the client systems, running <strong>phoronix-test-suite phoromatic.explore</strong> will also supply cache statistics.</p>
+<h3>Log Files</h3>
+<p>The Phoromatic Server will produce a log file of events / debugging information to <em>~/.phoronix-test-suite/phoromatic.log</em> or <em>/var/log/phoromatic.log</em> depending upon the service's permissions. When running the Phoronix Test Suite Phoromatic client, the log will be written to one of the respective locations in <em>phoronix-test-suite.log</em>.</p>
+<h3>Multi-User Accounts</h3>
+<p>For each time a user account is made from the Phoromatic web UI's log-in page, all of the test schedules, systems, and other account information is separate to allow for a completely isolated multi-user system. If a main administrator (the one creating the account) wishes to have multiple users sharing the same account data, that user can create additional accounts from the <em>Users</em> tab of their account. The main administrator can make an additional administrator account or a &quot;viewer&quot; account that can consume the account's data but not create/modify the schedules, systems, or other account details.</p>
+<h3>
+<h3>File Locations</h3>
+<p>When running the Phoronix Test Suite Phoromatic Server as root, rather than using the <em>~/.phoronix-test-suite/</em> directory, the standard Linux file-system hierarchy standard is honored. The main storage path is <em>/var/lib/phoronix-test-suite/</em>, the user configuration file is <em>/etc/phoronix-test-suite.xml</em>, and <em>/var/cache/phoronix-test-suite/</em> for cache files.</p>
+<h3>Uploading Other Test Results</h3>
+<p>Unscheduled test results and other results found on connected systems to a Phoromatic account can upload the data to the Phoromatic Server using the <em>phoronix-test-suite phoromatic.upload-result &lt;result file identifier &gt;</em> sub-command.</p>
+<h3>User Context File Logging</h3>
+<p>For those utilizing custom set context script files as part of the Phoromatic test schedule, any important notes / log information can be written to the file specified by the <em>PHOROMATIC_LOG_FILE</em> environment variable set while running the user context scripts. The contents of that file is then sent to the Phoromatic Server otherwise the standard output of the script's execution is submitted to the Phoromatic Server for logging. These logs can then be viewed by the Phoromatic Server along with the test results. Other environment variables accessible when running a user context script include <em>PHOROMATIC_TRIGGER</em>, <em>PHOROMATIC_SCHEDULE_ID</em>, and <em>PHOROMATIC_SCHEDULE_PROCESS</em>.</p>
 </body>
 </html>

install.bat

@@ -2,7 +2,7 @@
 
 :: Phoronix Test Suite
 :: URLs: http://www.phoronix.com, http://www.phoronix-test-suite.com/
-:: Copyright (C) 2018, Phoronix Media
+:: Copyright (C) 2018 - 2020, Phoronix Media
 ::
 :: This program is free software; you can redistribute it and/or modify
 :: it under the terms of the GNU General Public License as published by
@@ -29,5 +29,5 @@ md %destination%
 :: cd /d %destination%
 :: for /F "delims=" %%i in ('dir /b') do (rmdir "%%i" /s/q || del "%%i" /s/q)
 
-xcopy %cd% %destination% /E
+xcopy "%cd%" %destination% /E
 echo Phoronix Test Suite installed to %destination%

install_macos

@@ -0,0 +1,127 @@
+#!/bin/sh
+
+# Phoronix Test Suite
+# URLs: http://www.phoronix.com, http://www.phoronix-test-suite.com/
+# Copyright (C) 2008 - 2019, Phoronix Media
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+# Generic Phoronix Test Suite installer
+
+# To install into a chroot, set $DESTDIR to the corresponding directory.
+
+die() {
+	printf '%s\n' "$1" >&2
+	exit "${2:-1}"
+}
+
+if [ "X$1" = "X" ]
+then
+	INSTALL_PREFIX="/usr"
+else
+	INSTALL_PREFIX="$1"
+fi
+
+# Ensure the user is in the correct directory
+if [ ! -f pts-core/phoronix-test-suite.php ]
+then
+	die '
+	To install the Phoronix Test Suite you must first change directories to phoronix-test-suite/. For support visit: http://www.phoronix-test-suite.com/
+'
+fi
+
+mkdir -p "$DESTDIR$INSTALL_PREFIX"
+if [ ! -w "$DESTDIR$INSTALL_PREFIX" ]
+then
+	die "ERROR: $DESTDIR$INSTALL_PREFIX is not writable. Run this installer as root or specify a different directory prefix as the first argument sent to this script."
+fi
+
+rm -rf "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/
+rm -rf "$DESTDIR$INSTALL_PREFIX"/share/doc/phoronix-test-suite/
+
+mkdir -p "$DESTDIR$INSTALL_PREFIX"/bin/
+mkdir -p "$DESTDIR$INSTALL_PREFIX"/share/appdata/
+mkdir -p "$DESTDIR$INSTALL_PREFIX"/share/applications/
+mkdir -p "$DESTDIR$INSTALL_PREFIX"/share/icons/hicolor/48x48/apps/
+mkdir -p "$DESTDIR$INSTALL_PREFIX"/share/man/man1/
+mkdir -p "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/
+mkdir -p "$DESTDIR$INSTALL_PREFIX"/share/doc/phoronix-test-suite/
+mkdir -p "$DESTDIR$INSTALL_PREFIX"/../etc/bash_completion.d/
+#mkdir -p $DESTDIR$INSTALL_PREFIX/../usr/lib/systemd/system/
+#mkdir -p $DESTDIR$INSTALL_PREFIX/../etc/init/
+
+cp ChangeLog "$DESTDIR$INSTALL_PREFIX"/share/doc/phoronix-test-suite/
+cp COPYING "$DESTDIR$INSTALL_PREFIX"/share/doc/phoronix-test-suite/
+cp AUTHORS "$DESTDIR$INSTALL_PREFIX"/share/doc/phoronix-test-suite/
+
+cd documentation/ || exit
+cp -r * "$DESTDIR$INSTALL_PREFIX"/share/doc/phoronix-test-suite/
+cd ..
+rm -rf "$DESTDIR$INSTALL_PREFIX"/share/doc/phoronix-test-suite/man-pages/
+
+cp documentation/man-pages/*.1 "$DESTDIR$INSTALL_PREFIX"/share/man/man1/
+cp pts-core/static/bash_completion "$DESTDIR$INSTALL_PREFIX"/../etc/bash_completion.d/phoronix-test-suite
+cp pts-core/static/images/phoronix-test-suite.png "$DESTDIR$INSTALL_PREFIX"/share/icons/hicolor/48x48/apps/phoronix-test-suite.png
+cp pts-core/static/phoronix-test-suite.desktop "$DESTDIR$INSTALL_PREFIX"/share/applications/
+cp pts-core/static/phoronix-test-suite-launcher.desktop "$DESTDIR$INSTALL_PREFIX"/share/applications/
+cp pts-core/static/phoronix-test-suite.appdata.xml "$DESTDIR$INSTALL_PREFIX"/share/appdata/
+
+mkdir -p "$DESTDIR$INSTALL_PREFIX"/../usr/lib/systemd/system/
+cp deploy/*-systemd/*.service "$DESTDIR$INSTALL_PREFIX"/../usr/lib/systemd/system/
+
+# mkdir -p $DESTDIR$INSTALL_PREFIX/../etc/init/
+# cp pts-core/static/upstart/*.conf $DESTDIR$INSTALL_PREFIX/../etc/init/
+
+rm -rf "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/pts-core
+cp -r pts-core "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/
+cp -r ob-cache "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/
+cp -r deploy "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/
+rm -f "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/pts-core/static/phoronix-test-suite.desktop
+rm -f "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/pts-core/static/phoronix-test-suite-launcher.desktop
+rm -f "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/pts-core/openbenchmarking.org/openbenchmarking-mime.xml
+rm -f "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/pts-core/static/bash_completion
+rm -f "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/pts-core/static/images/openbenchmarking.png
+rm -f "$DESTDIR$INSTALL_PREFIX"/share/phoronix-test-suite/pts-core/static/images/%phoronix-test-suite.png
+
+
+sed -e 's:export PTS_DIR=$(actualpath "$(dirname "$0")"):export PTS_DIR='"$INSTALL_PREFIX"'\/share\/phoronix-test-suite:g'
+chmod +x "$DESTDIR$INSTALL_PREFIX"/bin/phoronix-test-suite
+
+# sed 's:\$url = PTS_PATH . \"documentation\/index.html\";:\$url = \"'"$INSTALL_PREFIX"'\/share\/doc\/packages\/phoronix-test-suite\/index.html\";:g' pts-core/commands/gui_gtk.php > $DESTDIR$INSTALL_PREFIX/share/phoronix-test-suite/pts-core/commands/gui_gtk.php
+
+# XDG MIME OpenBenchmarking support
+if [ "X$DESTDIR" = "X" ] && which xdg-mime >/dev/null && which xdg-icon-resource >/dev/null
+then
+	#No chroot
+	xdg-mime install pts-core/openbenchmarking.org/openbenchmarking-mime.xml
+	xdg-icon-resource install --context mimetypes --size 64 pts-core/static/images/openbenchmarking.png application-x-openbenchmarking
+else
+	#chroot
+	mkdir -p "$DESTDIR$INSTALL_PREFIX"/share/mime/packages/
+	mkdir -p "$DESTDIR$INSTALL_PREFIX"/share/icons/hicolor/64x64/mimetypes/
+	cp pts-core/openbenchmarking.org/openbenchmarking-mime.xml "$DESTDIR$INSTALL_PREFIX"/share/mime/packages/
+	cp pts-core/static/images/openbenchmarking.png "$DESTDIR$INSTALL_PREFIX"/share/icons/hicolor/64x64/mimetypes/application-x-openbenchmarking.png
+
+fi
+
+printf '%b\n' "\nPhoronix Test Suite Installation Completed\n
+Executable File: $INSTALL_PREFIX/bin/phoronix-test-suite
+Documentation: $INSTALL_PREFIX/share/doc/phoronix-test-suite/
+Phoronix Test Suite Files: $INSTALL_PREFIX/share/phoronix-test-suite/\n"
+
+if [ "X$DESTDIR" != "X" ]
+then
+	echo "Installed to chroot: $DESTDIR"
+	echo "Please update your desktop and mime-database manually"
+fi

ob-cache/openbenchmarking.org/git.index

@@ -1 +1 @@
-{"main":{"generated":1583166994},"tests":{"aom-av1":{"title":"AOM AV1","description":"This is a simple test of the AOMedia AV1 encoder run on the CPU with a sample video file.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux","MacOSX","BSD"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"713","last_updated":"1552063091","first_added":"1552063091","popularity":"1089","downloads":"1597","versions":["1.1.0"]},"dav1d":{"title":"dav1d","description":"Dav1d is an open-source, speedy AV1 video decoder. This test profile times how long it takes to decode sample AV1 video content.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux","BSD"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"612","last_updated":"1579721829","first_added":"1579697045","popularity":"517","downloads":1307,"versions":["1.0.1","1.0.0"]},"rav1e":{"title":"rav1e","description":"Xiph rav1e is a Rust-written AV1 video encoder.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux","MacOSX","BSD"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"709","last_updated":"1578155433","first_added":"1578155433","popularity":"543","downloads":"1659","versions":["1.0.0"]},"svt-av1":{"title":"SVT-AV1","description":"This is a test of the Intel Open Visual Cloud Scalable Video Technology SVT-AV1 CPU-based multi-threaded video encoder for the AV1 video format with a sample 1080p YUV video file. This test profile fork builds the encoder from Git source rather than a snapshot.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"135","last_updated":"1552059151","first_added":"1552059151","popularity":"1083","downloads":"1595","versions":["1.2.0"]},"svt-hevc":{"title":"SVT-HEVC","description":"This is a test of the Intel Open Visual Cloud Scalable Video Technology SVT-HEVC CPU-based multi-threaded video encoder for the HEVC \/ H.265 video format with a sample 1080p YUV video file. This test uses SVT-HEVC from Git master.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"55","last_updated":"1552060068","first_added":"1552060068","popularity":"1074","downloads":"1586","versions":["1.0.0"]},"svt-vp9":{"title":"SVT-VP9","description":"This is a test of the Intel Open Visual Cloud Scalable Video Technology SVT-VP9 CPU-based multi-threaded video encoder for the VP9 video format with a sample 1080p YUV video file. This test profile uses the Git snapshot of SVT-VP9.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"47","last_updated":"1552059681","first_added":"1552059681","popularity":"1087","downloads":"1584","versions":["1.0.0"]},"vpxenc":{"title":"VP9 libvpx Encoding","description":"This is a standard video encoding performance test of Google's libvpx library and the vpxenc command for the VP9\/WebM format using a sample 1080p video.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"778","last_updated":"1552061773","first_added":"1552061773","popularity":"1088","downloads":"1567","versions":["2.3.0"]},"x265":{"title":"x265","description":"This is a simple test of the x265 encoder run on the CPU with a sample 1080p video file.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux","MacOSX","BSD"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"124","last_updated":"1552061034","first_added":"1552061034","popularity":"1068","downloads":"1634","versions":["1.1.0"]}},"suites":[]}
+{"main":{"generated":1621076821},"tests":{"aom-av1":{"title":"AOM AV1","description":"This is a simple test of the AOMedia AV1 encoder run on the CPU with a sample video file.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux","MacOSX","BSD"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"786","average_install_time":"182","last_updated":"1552063091","first_added":"1552063091","popularity":"1554","downloads":"2138","versions":["1.1.0"]},"dav1d":{"title":"dav1d","description":"Dav1d is an open-source, speedy AV1 video decoder. This test profile times how long it takes to decode sample AV1 video content.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux","BSD"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"1531","average_install_time":"260","last_updated":"1579721829","first_added":"1579697045","popularity":"1347","downloads":3122,"versions":["1.0.1","1.0.0"]},"rav1e":{"title":"rav1e","description":"Xiph rav1e is a Rust-written AV1 video encoder.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux","MacOSX","BSD"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"651","average_install_time":"378","last_updated":"1578155433","first_added":"1578155433","popularity":"1302","downloads":"2715","versions":["1.0.0"]},"svt-av1":{"title":"SVT-AV1","description":"This is a test of the Intel Open Visual Cloud Scalable Video Technology SVT-AV1 CPU-based multi-threaded video encoder for the AV1 video format with a sample 1080p YUV video file. This test profile fork builds the encoder from Git source rather than a snapshot.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"167","average_install_time":"80","last_updated":"1552059151","first_added":"1552059151","popularity":"1539","downloads":"2130","versions":["1.2.0"]},"svt-hevc":{"title":"SVT-HEVC","description":"This is a test of the Intel Open Visual Cloud Scalable Video Technology SVT-HEVC CPU-based multi-threaded video encoder for the HEVC \/ H.265 video format with a sample 1080p YUV video file. This test uses SVT-HEVC from Git master.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"73","average_install_time":"53","last_updated":"1552060068","first_added":"1552060068","popularity":"1531","downloads":"2126","versions":["1.0.0"]},"svt-vp9":{"title":"SVT-VP9","description":"This is a test of the Intel Open Visual Cloud Scalable Video Technology SVT-VP9 CPU-based multi-threaded video encoder for the VP9 video format with a sample 1080p YUV video file. This test profile uses the Git snapshot of SVT-VP9.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"42","average_install_time":"50","last_updated":"1552059681","first_added":"1552059681","popularity":"1549","downloads":"2116","versions":["1.0.0"]},"vpxenc":{"title":"VP9 libvpx Encoding","description":"This is a standard video encoding performance test of Google's libvpx library and the vpxenc command for the VP9\/WebM format using a sample 1080p video.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"754","average_install_time":"76","last_updated":"1552061773","first_added":"1552061773","popularity":"1551","downloads":"2097","versions":["2.3.0"]},"x265":{"title":"x265","description":"This is a simple test of the x265 encoder run on the CPU with a sample 1080p video file.","test_type":"Processor","software_type":"Utility","status":"Verified","supported_platforms":["Linux","MacOSX","BSD"],"internal_tags":["SMP"],"test_extends":"","package_hash":null,"average_run_time":"361","average_install_time":"186","last_updated":"1552061034","first_added":"1552061034","popularity":"1512","downloads":"2177","versions":["1.1.0"]}},"suites":[]}

ob-cache/test-profiles/pts/ai-benchmark-1.0.0/install.sh

@@ -0,0 +1,25 @@
+#!/bin/bash
+
+if which pip3 >/dev/null 2>&1 ;
+then
+	echo 0 > ~/install-exit-status
+else
+	echo "ERROR: Python pip3 is not found on the system! This test profile needs Python pip3 to proceed."
+	echo 2 > ~/install-exit-status
+fi
+
+pip3 install --user tensorflow==2.2.0
+pip3 install --user ai-benchmark==0.1.2
+
+if [[ ! -f "$HOME/.local/bin/ai-benchmark" ]]
+then
+	echo "ERROR: AI-Benchmark failed to install on the system!"
+	echo 2 > ~/install-exit-status
+fi
+
+echo "#!/bin/bash
+
+cd \$HOME/.local/bin/
+python3 ./ai-benchmark > \$LOG_FILE 2>&1
+echo \$? > ~/test-exit-status" > ai-benchmark
+chmod +x ai-benchmark

ob-cache/test-profiles/pts/ai-benchmark-1.0.0/results-definition.xml

@@ -0,0 +1,16 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v9.8.0m2-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Device Inference Score: #_RESULT_#</OutputTemplate>
+    <ArgumentsDescription>Device Inference Score</ArgumentsDescription>
+  </ResultsParser>
+  <ResultsParser>
+    <OutputTemplate>Device Training Score: #_RESULT_#</OutputTemplate>
+    <ArgumentsDescription>Device Training Score</ArgumentsDescription>
+  </ResultsParser>
+  <ResultsParser>
+    <OutputTemplate>Device AI Score: #_RESULT_#</OutputTemplate>
+    <ArgumentsDescription>Device AI Score</ArgumentsDescription>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/ai-benchmark-1.0.0/test-definition.xml

@@ -0,0 +1,25 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v9.8.0m2-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>AI Benchmark Alpha</Title>
+    <AppVersion>0.1.2</AppVersion>
+    <Description>AI Benchmark Alpha is a Python library for evaluating artificial intelligence (AI) performance on diverse hardware platforms and relies upon the TensorFlow machine learning library.</Description>
+    <ResultScale>Score</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>1</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>1.0.0</Version>
+    <SupportedPlatforms>Linux, BSD, MacOSX</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>System</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>python</ExternalDependencies>
+    <RequiresInternet>TRUE</RequiresInternet>
+    <EnvironmentSize>10</EnvironmentSize>
+    <ProjectURL>http://ai-benchmark.com/alpha</ProjectURL>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/ai-benchmark-1.0.1/install.sh

@@ -0,0 +1,25 @@
+#!/bin/bash
+
+if which pip3 >/dev/null 2>&1 ;
+then
+	echo 0 > ~/install-exit-status
+else
+	echo "ERROR: Python pip3 is not found on the system! This test profile needs Python pip3 to proceed."
+	echo 2 > ~/install-exit-status
+fi
+
+pip3 install --user tensorflow==2.2.0
+pip3 install --user ai-benchmark==0.1.2
+
+if [[ ! -f "$HOME/.local/bin/ai-benchmark" ]]
+then
+	echo "ERROR: AI-Benchmark failed to install on the system!"
+	echo 2 > ~/install-exit-status
+fi
+
+echo "#!/bin/bash
+
+cd \$HOME/.local/bin/
+python3 ./ai-benchmark > \$LOG_FILE 2>&1
+echo \$? > ~/test-exit-status" > ai-benchmark
+chmod +x ai-benchmark

ob-cache/test-profiles/pts/ai-benchmark-1.0.1/install_macosx.sh

@@ -0,0 +1,24 @@
+#!/bin/bash
+
+if which pip3 >/dev/null 2>&1 ;
+then
+	echo 0 > ~/install-exit-status
+else
+	echo "ERROR: Python pip3 is not found on the system! This test profile needs Python pip3 to proceed."
+	echo 2 > ~/install-exit-status
+fi
+
+pip3 install --user tensorflow==2.2.0
+pip3 install --user ai-benchmark==0.1.2
+
+if [[ ! -f "$HOME/.local/bin/ai-benchmark" ]]
+then
+	echo "ERROR: AI-Benchmark failed to install on the system!"
+fi
+
+echo "#!/bin/bash
+
+cd \$HOME/Library/Python/3.*/bin/
+python3 ./ai-benchmark > \$LOG_FILE 2>&1
+echo \$? > ~/test-exit-status" > ai-benchmark
+chmod +x ai-benchmark

ob-cache/test-profiles/pts/ai-benchmark-1.0.1/results-definition.xml

@@ -0,0 +1,16 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.1-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Device Inference Score: #_RESULT_#</OutputTemplate>
+    <ArgumentsDescription>Device Inference Score</ArgumentsDescription>
+  </ResultsParser>
+  <ResultsParser>
+    <OutputTemplate>Device Training Score: #_RESULT_#</OutputTemplate>
+    <ArgumentsDescription>Device Training Score</ArgumentsDescription>
+  </ResultsParser>
+  <ResultsParser>
+    <OutputTemplate>Device AI Score: #_RESULT_#</OutputTemplate>
+    <ArgumentsDescription>Device AI Score</ArgumentsDescription>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/ai-benchmark-1.0.1/test-definition.xml

@@ -0,0 +1,25 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.1-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>AI Benchmark Alpha</Title>
+    <AppVersion>0.1.2</AppVersion>
+    <Description>AI Benchmark Alpha is a Python library for evaluating artificial intelligence (AI) performance on diverse hardware platforms and relies upon the TensorFlow machine learning library.</Description>
+    <ResultScale>Score</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>1</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>1.0.1</Version>
+    <SupportedPlatforms>Linux, BSD, MacOSX</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>System</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>python</ExternalDependencies>
+    <RequiresInternet>TRUE</RequiresInternet>
+    <EnvironmentSize>10</EnvironmentSize>
+    <ProjectURL>http://ai-benchmark.com/alpha</ProjectURL>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aio-stress-1.1.2/downloads.xml

@@ -0,0 +1,12 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.0m2-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://fsbench.filesystems.org/bench/aio-stress.c</URL>
+      <MD5>727e5fc3566837b3ea72f887d048769b</MD5>
+      <FileName>aio-stress.c</FileName>
+      <FileSize>39513</FileSize>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aio-stress-1.1.2/install.sh

@@ -0,0 +1,11 @@
+#!/bin/sh
+
+cc -Wall -O3 -pthread -o aio-stress-bin aio-stress.c -laio
+echo $? > ~/install-exit-status
+
+# add support for allowing aio-test-file to be on removable media devices
+echo "#!/bin/sh
+./aio-stress-bin \$@ aio-test-file > \$LOG_FILE 2>&1
+echo \$? > ~/test-exit-status
+rm -f aio-test-file" > aio-stress
+chmod +x aio-stress

ob-cache/test-profiles/pts/aio-stress-1.1.2/results-definition.xml

@@ -0,0 +1,16 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.0m2-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>adding stage random write
+dropping thread count to the number of contexts 1
+starting with random write
+file size 1024MB, record size 64KB, depth 64, ios per iteration 8
+max io_submit 8, buffer alignment set to 4KB
+threads 1 files 1 contexts 1 context offset 2MB verification off
+random write on aio-test-file (#_RESULT_# MB/s) 1024.00 MB in 3.84s
+thread 0 random write totals (63.36 MB/s) 1024.00 MB in 16.16s
+Running single thread version</OutputTemplate>
+    <LineHint>random write on aio-test-file</LineHint>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aio-stress-1.1.2/test-definition.xml

@@ -0,0 +1,40 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.0m2-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>AIO-Stress</Title>
+    <AppVersion>0.21</AppVersion>
+    <Description>AIO-Stress is an a-synchronous I/O benchmark created by SuSE. Current this profile uses a 2048MB test file and a 64KB record size.</Description>
+    <ResultScale>MB/s</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>1.1.2</Version>
+    <SupportedPlatforms>Linux</SupportedPlatforms>
+    <SoftwareType>Benchmark</SoftwareType>
+    <TestType>Disk</TestType>
+    <License>Free</License>
+    <Status>Deprecated</Status>
+    <ExternalDependencies>build-utilities, libaio-development</ExternalDependencies>
+    <EnvironmentSize>0.5</EnvironmentSize>
+    <EnvironmentTestingSize>1024</EnvironmentTestingSize>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Default>
+      <Arguments>-s 2g -r 64k -t 3</Arguments>
+    </Default>
+    <Option>
+      <DisplayName>Test</DisplayName>
+      <Identifier>test</Identifier>
+      <ArgumentPrefix>-o </ArgumentPrefix>
+      <Menu>
+        <Entry>
+          <Name>Random Write</Name>
+          <Value>2</Value>
+        </Entry>
+      </Menu>
+    </Option>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aircrack-ng-1.2.1/downloads.xml

@@ -0,0 +1,22 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v9.6.0-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://download.aircrack-ng.org/aircrack-ng-1.5.2.tar.gz</URL>
+      <MD5>2648c192d206e953c67dca64967d2982</MD5>
+      <SHA256>9e592fe7658046220e0ac0a6d05c4026903f3077b248893e0056ccbe4ee88241</SHA256>
+      <FileName>aircrack-ng-1.5.2.tar.gz</FileName>
+      <FileSize>7138360</FileSize>
+      <PlatformSpecific>Linux, BSD</PlatformSpecific>
+    </Package>
+    <Package>
+      <URL>http://download.aircrack-ng.org/aircrack-ng-1.5.2-win.zip</URL>
+      <MD5>4c705429ca51e79b490f1dca863d2217</MD5>
+      <SHA256>61a91b44918eb196f06f46a3dbc359ddeced5712095c814fabc473b25a1c2e44</SHA256>
+      <FileName>aircrack-ng-1.5.2-win.zip</FileName>
+      <FileSize>16903422</FileSize>
+      <PlatformSpecific>Windows</PlatformSpecific>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aircrack-ng-1.2.1/install.sh

@@ -0,0 +1,26 @@
+#!/bin/sh
+tar -xf aircrack-ng-1.5.2.tar.gz
+cd aircrack-ng-1.5.2
+export CFLAGS="-O3 -fcommon"
+export CXXFLAGS="-O3 -fcommon"
+if [ "$OS_TYPE" = "BSD" ]
+then
+	if [ -e /usr/local/lib/libcrypto.so ]
+	then
+		env MAKE=gmake CFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib ./autogen.sh
+	else
+		env MAKE=gmake ./autogen.sh
+	fi
+	gmake -j $NUM_CPU_CORES
+else
+	./autogen.sh
+	make -j $NUM_CPU_CORES
+fi
+echo $? > ~/install-exit-status
+
+cd ~
+echo "#!/bin/sh
+cd aircrack-ng-1.5.2
+./src/aircrack-ng -p \$NUM_CPU_CORES \$@  2>&1 | tr '\\r' '\\n' | awk -v max=0 '{if(\$1>max){max=\$1}}END{print max \" k/s\"}' > \$LOG_FILE
+echo \$? > ~/test-exit-status" > aircrack-ng
+chmod +x aircrack-ng

ob-cache/test-profiles/pts/aircrack-ng-1.2.1/install_windows.sh

@@ -0,0 +1,8 @@
+#!/bin/sh
+unzip -o aircrack-ng-1.5.2-win.zip
+
+echo "#!/bin/sh
+cd aircrack-ng-1.5.2-win
+./bin/64bit/aircrack-ng.exe \$@  2>&1 | tr '\\r' '\\n' | awk -v max=0 '{if(\$1>max){max=\$1}}END{print max \" k/s\"}' > \$LOG_FILE
+echo \$? > ~/test-exit-status" > aircrack-ng
+chmod +x aircrack-ng

ob-cache/test-profiles/pts/aircrack-ng-1.2.1/results-definition.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v9.6.0-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>#_RESULT_# k/s</OutputTemplate>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aircrack-ng-1.2.1/test-definition.xml

@@ -0,0 +1,29 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v9.6.0-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>Aircrack-ng</Title>
+    <AppVersion>1.5.2</AppVersion>
+    <Description>Aircrack-ng is a tool for assessing WiFi/WLAN network security.</Description>
+    <ResultScale>k/s</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>1.2.1</Version>
+    <SupportedPlatforms>Linux, BSD, Windows</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>Processor</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>build-utilities, openssl-development, libtool</ExternalDependencies>
+    <EnvironmentSize>25</EnvironmentSize>
+    <ProjectURL>http://www.aircrack-ng.org/</ProjectURL>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Default>
+      <Arguments>-S -Z 30</Arguments>
+    </Default>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/amg-1.1.0/downloads.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.0-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/AMG-20200304.tar.xz</URL>
+      <MD5>aa0b1856f5f2d5c7e9250de8a4ef5084</MD5>
+      <SHA256>918964262a30023b65a1e67efc15ec7e434d48c3e886497d1fb2b2fb131043f8</SHA256>
+      <FileName>AMG-20200304.tar.xz</FileName>
+      <FileSize>1311336</FileSize>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/amg-1.1.0/install.sh

@@ -0,0 +1,24 @@
+#!/bin/sh
+
+tar -xf AMG-20200304.tar.xz
+rm -rf AMG-bin
+mv AMG AMG-bin
+cd AMG-bin
+make -j $NUM_CPU_CORES
+echo $? > ~/install-exit-status
+
+cd ~/
+cat>amg<<EOT
+#!/bin/sh
+cd AMG-bin
+
+if [ "\$NUM_CPU_CORES" -gt "\$NUM_CPU_PHYSICAL_CORES" ]; then
+	export OMP_NUM_THREADS=2
+else
+	export OMP_NUM_THREADS=1
+fi
+mpirun --allow-run-as-root -np \$NUM_CPU_PHYSICAL_CORES ./test/amg -n 96 96 96 > \$LOG_FILE 2>&1
+echo \$? > ~/test-exit-status
+EOT
+chmod +x amg
+

ob-cache/test-profiles/pts/amg-1.1.0/results-definition.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.0-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Figure of Merit (FOM_1): #_RESULT_#</OutputTemplate>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/amg-1.1.0/test-definition.xml

@@ -0,0 +1,24 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.0-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>Algebraic Multi-Grid Benchmark</Title>
+    <AppVersion>1.2</AppVersion>
+    <Description>AMG is a parallel algebraic multigrid solver for linear systems arising from problems on unstructured grids.  The driver provided with AMG builds linear systems for various 3-dimensional problems.</Description>
+    <ResultScale>Figure Of Merit</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>1.1.0</Version>
+    <SupportedPlatforms>Linux</SupportedPlatforms>
+    <SoftwareType>Scientific</SoftwareType>
+    <TestType>Processor</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>openmpi-development, build-utilities</ExternalDependencies>
+    <EnvironmentSize>10</EnvironmentSize>
+    <ProjectURL>https://github.com/LLNL/AMG</ProjectURL>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.1.1/downloads.xml

@@ -0,0 +1,28 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v9.6.0-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://ultravideo.cs.tut.fi/video/Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z</URL>
+      <MD5>84ae521c95aa2537e16b34bbf72f2def</MD5>
+      <SHA256>e2f60b904789a60f6d1edc194d8540d401dd882e3ee3605b9b1de8feacc72133</SHA256>
+      <FileName>Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z</FileName>
+      <FileSize>676792531</FileSize>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/aom-200.tar.xz</URL>
+      <MD5>93c614944b53ed69f36439e433411ddc</MD5>
+      <SHA256>8996bb24c5768a109e3d20cb4b7adb617d7a4095e11801cef1ffccba5e5e6e2c</SHA256>
+      <FileName>aom-200.tar.xz</FileName>
+      <FileSize>2390800</FileSize>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/aom-200-windows.zip</URL>
+      <MD5>693fe89d844c2735c347b78d3b2df32f</MD5>
+      <SHA256>b27e905f990dffb4071475b0129809ab30f49ed578e69857af61c63400a8572b</SHA256>
+      <FileName>aom-200-windows.zip</FileName>
+      <FileSize>3691863</FileSize>
+      <PlatformSpecific>Windows</PlatformSpecific>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.1.1/install.sh

@@ -0,0 +1,24 @@
+#!/bin/sh
+
+tar -xf aom-200.tar.xz
+cd aom/build
+cmake ..
+make -j $NUM_CPU_CORES
+echo $? > ~/install-exit-status
+cd ~
+
+7z x Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z
+
+# Current AOMedia Git has MAX_NUM_THREADS value of 64, don't go over 64 threads or error
+
+echo "#!/bin/sh
+
+if [ \"\$NUM_CPU_CORES\" -gt 64 ]; then
+	NUM_CPU_CORES=64
+fi
+
+./aom/build/aomenc --threads=\$NUM_CPU_CORES \$@ -o test.av1 Bosphorus_1920x1080_120fps_420_8bit_YUV.y4m > 1.log 2>&1
+echo \$? > ~/test-exit-status
+sed \$'s/[^[:print:]\t]/\\n/g' 1.log > \$LOG_FILE
+rm -f test.av1" > aom-av1
+chmod +x aom-av1

ob-cache/test-profiles/pts/aom-av1-2.1.1/install_windows.sh

@@ -0,0 +1,17 @@
+#!/bin/sh
+
+unzip -o aom-200-windows.zip
+7z x Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z
+chmod +x aomenc.exe
+
+echo "#!/bin/sh
+
+if [ \"\$NUM_CPU_CORES\" -gt 64 ]; then
+	NUM_CPU_CORES=64
+fi
+
+./aomenc.exe --threads=\$NUM_CPU_CORES \$@ -o test.av1 Bosphorus_1920x1080_120fps_420_8bit_YUV.y4m > 1.log 2>&1
+echo \$? > ~/test-exit-status
+sed \$'s/[^[:print:]\t]/\\n/g' 1.log > \$LOG_FILE
+rm -f test.av1" > aom-av1
+chmod +x aom-av1

ob-cache/test-profiles/pts/aom-av1-2.1.1/results-definition.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v9.6.0-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Pass 1/2 frame    3/4        768B    2048b/f   61440b/s  165907 us #_RESULT_# fps)</OutputTemplate>
+    <LineHint>fps</LineHint>
+    <TurnCharsToSpace>(</TurnCharsToSpace>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.1.1/test-definition.xml

@@ -0,0 +1,56 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v9.6.0-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>AOM AV1</Title>
+    <AppVersion>2.0</AppVersion>
+    <Description>This is a simple test of the AOMedia AV1 encoder run on the CPU with a sample video file.</Description>
+    <ResultScale>Frames Per Second</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>2.1.1</Version>
+    <SupportedPlatforms>Linux, MacOSX, BSD, Windows</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>Processor</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>build-utilities, p7zip, cmake, perl, yasm</ExternalDependencies>
+    <EnvironmentSize>950</EnvironmentSize>
+    <ProjectURL>https://aomedia.googlesource.com/aom/</ProjectURL>
+    <InternalTags>SMP</InternalTags>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Default>
+      <Arguments>--tile-columns=2 --tile-rows=1</Arguments>
+    </Default>
+    <Option>
+      <DisplayName>Encoder Mode</DisplayName>
+      <Identifier>enc-mode</Identifier>
+      <Menu>
+        <Entry>
+          <Name>Speed 8 Realtime</Name>
+          <Value>--cpu-used=8 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 6 Realtime</Name>
+          <Value>--cpu-used=6 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 6 Two-Pass</Name>
+          <Value>--cpu-used=6 --limit=80</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 4 Two-Pass</Name>
+          <Value>--cpu-used=4 --limit=40</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 0 Two-Pass</Name>
+          <Value>--cpu-used=0 --limit=10</Value>
+        </Entry>
+      </Menu>
+    </Option>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.1.2/downloads.xml

@@ -0,0 +1,28 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.0m1-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://ultravideo.cs.tut.fi/video/Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z</URL>
+      <MD5>84ae521c95aa2537e16b34bbf72f2def</MD5>
+      <SHA256>e2f60b904789a60f6d1edc194d8540d401dd882e3ee3605b9b1de8feacc72133</SHA256>
+      <FileName>Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z</FileName>
+      <FileSize>676792531</FileSize>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/aom-200.tar.xz</URL>
+      <MD5>93c614944b53ed69f36439e433411ddc</MD5>
+      <SHA256>8996bb24c5768a109e3d20cb4b7adb617d7a4095e11801cef1ffccba5e5e6e2c</SHA256>
+      <FileName>aom-200.tar.xz</FileName>
+      <FileSize>2390800</FileSize>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/aom-200-windows.zip</URL>
+      <MD5>693fe89d844c2735c347b78d3b2df32f</MD5>
+      <SHA256>b27e905f990dffb4071475b0129809ab30f49ed578e69857af61c63400a8572b</SHA256>
+      <FileName>aom-200-windows.zip</FileName>
+      <FileSize>3691863</FileSize>
+      <PlatformSpecific>Windows</PlatformSpecific>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.1.2/install.sh

@@ -0,0 +1,24 @@
+#!/bin/sh
+
+tar -xf aom-200.tar.xz
+cd aom/build
+cmake -DENABLE_DOCS=0 -DENABLE_TESTS=0 -DCONFIG_AV1_DECODER=0 ..
+make -j $NUM_CPU_CORES
+echo $? > ~/install-exit-status
+cd ~
+
+7z x Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z
+
+# Current AOMedia Git has MAX_NUM_THREADS value of 64, don't go over 64 threads or error
+
+echo "#!/bin/sh
+
+if [ \"\$NUM_CPU_CORES\" -gt 64 ]; then
+	NUM_CPU_CORES=64
+fi
+
+./aom/build/aomenc --threads=\$NUM_CPU_CORES \$@ -o test.av1 Bosphorus_1920x1080_120fps_420_8bit_YUV.y4m > 1.log 2>&1
+echo \$? > ~/test-exit-status
+sed \$'s/[^[:print:]\t]/\\n/g' 1.log > \$LOG_FILE
+rm -f test.av1" > aom-av1
+chmod +x aom-av1

ob-cache/test-profiles/pts/aom-av1-2.1.2/install_windows.sh

@@ -0,0 +1,17 @@
+#!/bin/sh
+
+unzip -o aom-200-windows.zip
+7z x Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z
+chmod +x aomenc.exe
+
+echo "#!/bin/sh
+
+if [ \"\$NUM_CPU_CORES\" -gt 64 ]; then
+	NUM_CPU_CORES=64
+fi
+
+./aomenc.exe --threads=\$NUM_CPU_CORES \$@ -o test.av1 Bosphorus_1920x1080_120fps_420_8bit_YUV.y4m > 1.log 2>&1
+echo \$? > ~/test-exit-status
+sed \$'s/[^[:print:]\t]/\\n/g' 1.log > \$LOG_FILE
+rm -f test.av1" > aom-av1
+chmod +x aom-av1

ob-cache/test-profiles/pts/aom-av1-2.1.2/results-definition.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.0m1-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Pass 1/2 frame    3/4        768B    2048b/f   61440b/s  165907 us #_RESULT_# fps)</OutputTemplate>
+    <LineHint>fps</LineHint>
+    <TurnCharsToSpace>(</TurnCharsToSpace>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.1.2/test-definition.xml

@@ -0,0 +1,56 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.0m1-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>AOM AV1</Title>
+    <AppVersion>2.0</AppVersion>
+    <Description>This is a simple test of the AOMedia AV1 encoder run on the CPU with a sample video file.</Description>
+    <ResultScale>Frames Per Second</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>2.1.2</Version>
+    <SupportedPlatforms>Linux, MacOSX, BSD, Windows</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>Processor</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>build-utilities, p7zip, cmake, perl, yasm</ExternalDependencies>
+    <EnvironmentSize>950</EnvironmentSize>
+    <ProjectURL>https://aomedia.googlesource.com/aom/</ProjectURL>
+    <InternalTags>SMP</InternalTags>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Default>
+      <Arguments>--tile-columns=2 --tile-rows=1</Arguments>
+    </Default>
+    <Option>
+      <DisplayName>Encoder Mode</DisplayName>
+      <Identifier>enc-mode</Identifier>
+      <Menu>
+        <Entry>
+          <Name>Speed 8 Realtime</Name>
+          <Value>--cpu-used=8 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 6 Realtime</Name>
+          <Value>--cpu-used=6 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 6 Two-Pass</Name>
+          <Value>--cpu-used=6 --limit=80</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 4 Two-Pass</Name>
+          <Value>--cpu-used=4 --limit=40</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 0 Two-Pass</Name>
+          <Value>--cpu-used=0 --limit=10</Value>
+        </Entry>
+      </Menu>
+    </Option>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.2.0/downloads.xml

@@ -0,0 +1,28 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.2-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://ultravideo.cs.tut.fi/video/Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z</URL>
+      <MD5>84ae521c95aa2537e16b34bbf72f2def</MD5>
+      <SHA256>e2f60b904789a60f6d1edc194d8540d401dd882e3ee3605b9b1de8feacc72133</SHA256>
+      <FileName>Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z</FileName>
+      <FileSize>676792531</FileSize>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/aom-201-rc1-20210312.tar.xz</URL>
+      <MD5>75518c301a0a8ea6e309db6b1672f27a</MD5>
+      <SHA256>b4251908484c9d74333141fec5c8e68cc768514baf2b876d2a069f0d6b280db9</SHA256>
+      <FileName>aom-201-rc1-20210312.tar.xz</FileName>
+      <FileSize>3268248</FileSize>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/aom-201-rc1-20210312-win64.zip</URL>
+      <MD5>6a406b60af254502749c5d902b2325e7</MD5>
+      <SHA256>b58e88009ce7f063c572fe82aeec27ae31e6e4cacba19f733f935ee07b0bada0</SHA256>
+      <FileName>aom-201-rc1-20210312-win64.zip</FileName>
+      <FileSize>4022090</FileSize>
+      <PlatformSpecific>Windows</PlatformSpecific>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.2.0/install.sh

@@ -0,0 +1,24 @@
+#!/bin/sh
+
+tar -xf aom-201-rc1-20210312.tar.xz
+cd aom/build
+cmake -DENABLE_DOCS=0 -DENABLE_TESTS=0 -DCONFIG_AV1_DECODER=0 -DCMAKE_BUILD_TYPE=Release ..
+make -j $NUM_CPU_CORES
+echo $? > ~/install-exit-status
+cd ~
+
+7z x Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z
+
+# Current AOMedia Git has MAX_NUM_THREADS value of 64, don't go over 64 threads or error
+
+echo "#!/bin/sh
+
+if [ \"\$NUM_CPU_CORES\" -gt 64 ]; then
+	NUM_CPU_CORES=64
+fi
+
+./aom/build/aomenc --threads=\$NUM_CPU_CORES \$@ -o test.av1 Bosphorus_1920x1080_120fps_420_8bit_YUV.y4m > 1.log 2>&1
+echo \$? > ~/test-exit-status
+sed \$'s/[^[:print:]\t]/\\n/g' 1.log > \$LOG_FILE
+rm -f test.av1" > aom-av1
+chmod +x aom-av1

ob-cache/test-profiles/pts/aom-av1-2.2.0/install_windows.sh

@@ -0,0 +1,17 @@
+#!/bin/sh
+
+unzip -o aom-201-rc1-20210312-win64.zip
+7z x Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z
+chmod +x aomenc.exe
+
+echo "#!/bin/sh
+
+if [ \"\$NUM_CPU_CORES\" -gt 64 ]; then
+	NUM_CPU_CORES=64
+fi
+
+./aomenc.exe --threads=\$NUM_CPU_CORES \$@ -o test.av1 Bosphorus_1920x1080_120fps_420_8bit_YUV.y4m > 1.log 2>&1
+echo \$? > ~/test-exit-status
+sed \$'s/[^[:print:]\t]/\\n/g' 1.log > \$LOG_FILE
+rm -f test.av1" > aom-av1
+chmod +x aom-av1

ob-cache/test-profiles/pts/aom-av1-2.2.0/results-definition.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.2-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Pass 1/2 frame    3/4        768B    2048b/f   61440b/s  165907 us #_RESULT_# fps)</OutputTemplate>
+    <LineHint>fps</LineHint>
+    <TurnCharsToSpace>(</TurnCharsToSpace>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.2.0/test-definition.xml

@@ -0,0 +1,57 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.2-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>AOM AV1</Title>
+    <AppVersion>2.1-rc</AppVersion>
+    <Description>This is a test of the AOMedia AV1 encoder (libaom) run on the CPU with a sample 1080p video file.</Description>
+    <ResultScale>Frames Per Second</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>2.2.0</Version>
+    <SupportedPlatforms>Linux, MacOSX, BSD, Windows</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>Processor</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>build-utilities, p7zip, cmake, perl, yasm</ExternalDependencies>
+    <EnvironmentSize>950</EnvironmentSize>
+    <ProjectURL>https://aomedia.googlesource.com/aom/</ProjectURL>
+    <InternalTags>SMP</InternalTags>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Default>
+      <Arguments>--tile-columns=2 --tile-rows=2 --row-mt=1</Arguments>
+    </Default>
+    <Option>
+      <DisplayName>Encoder Mode</DisplayName>
+      <Identifier>enc-mode</Identifier>
+      <Menu>
+        <Entry>
+          <Name>Speed 8 Realtime</Name>
+          <Value>--cpu-used=8 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 6 Realtime</Name>
+          <Value>--cpu-used=6 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 6 Two-Pass</Name>
+          <Value>--cpu-used=6</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 4 Two-Pass</Name>
+          <Value>--cpu-used=4</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 0 Two-Pass</Name>
+          <Value>--cpu-used=0 --limit=20</Value>
+          <Message>Slowest</Message>
+        </Entry>
+      </Menu>
+    </Option>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.3.0/downloads.xml

@@ -0,0 +1,35 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.4.0m1-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://ultravideo.cs.tut.fi/video/Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z</URL>
+      <MD5>84ae521c95aa2537e16b34bbf72f2def</MD5>
+      <SHA256>e2f60b904789a60f6d1edc194d8540d401dd882e3ee3605b9b1de8feacc72133</SHA256>
+      <FileName>Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z</FileName>
+      <FileSize>676792531</FileSize>
+    </Package>
+    <Package>
+      <URL>http://ultravideo.cs.tut.fi/video/Bosphorus_3840x2160_120fps_420_8bit_YUV_Y4M.7z</URL>
+      <MD5>815ca5830c8ea2f95545429817b96b1f</MD5>
+      <SHA256>d0fcb7d8cfc6e51c47ce8b427dab41ce38300c4b1a51a1903ddd5d86067c4c79</SHA256>
+      <FileName>Bosphorus_3840x2160_120fps_420_8bit_YUV_Y4M.7z</FileName>
+      <FileSize>2804470345</FileSize>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/aom-300.tar.xz</URL>
+      <MD5>8b2d66ffcff3bd421ab6d8007af90eb7</MD5>
+      <SHA256>cd38b59fc8ede3f76a89fa4b60f5a45c04cc05591899a2fa875c7b4e8a949a9e</SHA256>
+      <FileName>aom-300.tar.xz</FileName>
+      <FileSize>3275012</FileSize>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/aom-300-win64.zip</URL>
+      <MD5>15410151c873c477d067dfcd9463777e</MD5>
+      <SHA256>a2fd536c7e6a6bbbc5dc656251fd21e8e4a3073b9a7a0afe96d7bff8e16bc0ee</SHA256>
+      <FileName>aom-300-win64.zip</FileName>
+      <FileSize>4048267</FileSize>
+      <PlatformSpecific>Windows</PlatformSpecific>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.3.0/install.sh

@@ -0,0 +1,26 @@
+#!/bin/sh
+
+tar -xf aom-300.tar.xz
+cd aom/build
+cmake -DENABLE_DOCS=0 -DENABLE_TESTS=0 -DCONFIG_AV1_DECODER=0 -DCMAKE_BUILD_TYPE=Release ..
+make -j $NUM_CPU_CORES
+echo $? > ~/install-exit-status
+cd ~
+
+7z x Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z
+rm -f Bosphorus_Copyright.txt
+7z x Bosphorus_3840x2160_120fps_420_8bit_YUV_Y4M.7z
+
+# Current AOMedia Git has MAX_NUM_THREADS value of 64, don't go over 64 threads or error
+
+echo "#!/bin/sh
+
+if [ \"\$NUM_CPU_CORES\" -gt 64 ]; then
+	NUM_CPU_CORES=64
+fi
+
+./aom/build/aomenc --threads=\$NUM_CPU_CORES -o test.av1 \$@ > 1.log 2>&1
+echo \$? > ~/test-exit-status
+sed \$'s/[^[:print:]\t]/\\n/g' 1.log > \$LOG_FILE
+rm -f test.av1" > aom-av1
+chmod +x aom-av1

ob-cache/test-profiles/pts/aom-av1-2.3.0/install_windows.sh

@@ -0,0 +1,20 @@
+#!/bin/sh
+
+unzip -o aom-300-win64.zip
+chmod +x aomenc.exe
+
+7z x Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z
+rm -f Bosphorus_Copyright.txt
+7z x Bosphorus_3840x2160_120fps_420_8bit_YUV_Y4M.7z
+
+echo "#!/bin/sh
+
+if [ \"\$NUM_CPU_CORES\" -gt 64 ]; then
+	NUM_CPU_CORES=64
+fi
+
+./aomenc.exe --threads=\$NUM_CPU_CORES -o test.av1 \$@ > 1.log 2>&1
+echo \$? > ~/test-exit-status
+sed \$'s/[^[:print:]\t]/\\n/g' 1.log > \$LOG_FILE
+rm -f test.av1" > aom-av1
+chmod +x aom-av1

ob-cache/test-profiles/pts/aom-av1-2.3.0/results-definition.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.4.0m1-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Pass 1/2 frame    3/4        768B    2048b/f   61440b/s  165907 us #_RESULT_# fps)</OutputTemplate>
+    <LineHint>fps</LineHint>
+    <TurnCharsToSpace>(</TurnCharsToSpace>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.3.0/test-definition.xml

@@ -0,0 +1,75 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.4.0m1-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>AOM AV1</Title>
+    <AppVersion>3.0</AppVersion>
+    <Description>This is a test of the AOMedia AV1 encoder (libaom) developed by AOMedia and Google.</Description>
+    <ResultScale>Frames Per Second</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>2.3.0</Version>
+    <SupportedPlatforms>Linux, MacOSX, BSD, Windows</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>Processor</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>build-utilities, p7zip, cmake, perl, yasm</ExternalDependencies>
+    <EnvironmentSize>1950</EnvironmentSize>
+    <ProjectURL>https://aomedia.googlesource.com/aom/</ProjectURL>
+    <InternalTags>SMP</InternalTags>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Default>
+      <Arguments>--tile-columns=2 --tile-rows=2 --row-mt=1</Arguments>
+    </Default>
+    <Option>
+      <DisplayName>Encoder Mode</DisplayName>
+      <Identifier>enc-mode</Identifier>
+      <Menu>
+        <Entry>
+          <Name>Speed 9 Realtime</Name>
+          <Value>--cpu-used=9 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 8 Realtime</Name>
+          <Value>--cpu-used=8 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 6 Realtime</Name>
+          <Value>--cpu-used=6 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 6 Two-Pass</Name>
+          <Value>--cpu-used=6</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 4 Two-Pass</Name>
+          <Value>--cpu-used=4</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 0 Two-Pass</Name>
+          <Value>--cpu-used=0 --limit=20</Value>
+          <Message>Slowest</Message>
+        </Entry>
+      </Menu>
+    </Option>
+    <Option>
+      <DisplayName>Input</DisplayName>
+      <Identifier>input</Identifier>
+      <Menu>
+        <Entry>
+          <Name>Bosphorus 1080p</Name>
+          <Value>Bosphorus_1920x1080_120fps_420_8bit_YUV.y4m</Value>
+        </Entry>
+        <Entry>
+          <Name>Bosphorus 4K</Name>
+          <Value>Bosphorus_3840x2160.y4m</Value>
+        </Entry>
+      </Menu>
+    </Option>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.4.0/downloads.xml

@@ -0,0 +1,35 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.4.0m1-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://ultravideo.cs.tut.fi/video/Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z</URL>
+      <MD5>84ae521c95aa2537e16b34bbf72f2def</MD5>
+      <SHA256>e2f60b904789a60f6d1edc194d8540d401dd882e3ee3605b9b1de8feacc72133</SHA256>
+      <FileName>Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z</FileName>
+      <FileSize>676792531</FileSize>
+    </Package>
+    <Package>
+      <URL>http://ultravideo.cs.tut.fi/video/Bosphorus_3840x2160_120fps_420_8bit_YUV_Y4M.7z</URL>
+      <MD5>815ca5830c8ea2f95545429817b96b1f</MD5>
+      <SHA256>d0fcb7d8cfc6e51c47ce8b427dab41ce38300c4b1a51a1903ddd5d86067c4c79</SHA256>
+      <FileName>Bosphorus_3840x2160_120fps_420_8bit_YUV_Y4M.7z</FileName>
+      <FileSize>2804470345</FileSize>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/aom-310.tar.xz</URL>
+      <MD5>97ec2d870dbd79eae847397a4033191b</MD5>
+      <SHA256>2f68838fdce56022d867f09a2c612f67a3075e2b15ef64797293358a34dbc9ca</SHA256>
+      <FileName>aom-310.tar.xz</FileName>
+      <FileSize>3296804</FileSize>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/aom-310-win64.zip</URL>
+      <MD5>7b7aa1f8d64f8a9e0f83cbef82370f82</MD5>
+      <SHA256>eb2765db33fcbca79466d8f29f28be6b95f1a7d2ade0ee67f0ebaf190f73dfd8</SHA256>
+      <FileName>aom-310-win64.zip</FileName>
+      <FileSize>4113883</FileSize>
+      <PlatformSpecific>Windows</PlatformSpecific>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.4.0/install.sh

@@ -0,0 +1,26 @@
+#!/bin/sh
+
+tar -xf aom-310.tar.xz
+cd aom/build
+cmake -DENABLE_DOCS=0 -DENABLE_TESTS=0 -DCONFIG_AV1_DECODER=0 -DCMAKE_BUILD_TYPE=Release ..
+make -j $NUM_CPU_CORES
+echo $? > ~/install-exit-status
+cd ~
+
+7z x Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z
+rm -f Bosphorus_Copyright.txt
+7z x Bosphorus_3840x2160_120fps_420_8bit_YUV_Y4M.7z
+
+# Current AOMedia Git has MAX_NUM_THREADS value of 64, don't go over 64 threads or error
+
+echo "#!/bin/sh
+
+if [ \"\$NUM_CPU_CORES\" -gt 64 ]; then
+	NUM_CPU_CORES=64
+fi
+
+./aom/build/aomenc --threads=\$NUM_CPU_CORES -o test.av1 \$@ > 1.log 2>&1
+echo \$? > ~/test-exit-status
+sed \$'s/[^[:print:]\t]/\\n/g' 1.log > \$LOG_FILE
+rm -f test.av1" > aom-av1
+chmod +x aom-av1

ob-cache/test-profiles/pts/aom-av1-2.4.0/install_windows.sh

@@ -0,0 +1,20 @@
+#!/bin/sh
+
+unzip -o aom-310-win64.zip
+chmod +x aomenc.exe
+
+7z x Bosphorus_1920x1080_120fps_420_8bit_YUV_Y4M.7z
+rm -f Bosphorus_Copyright.txt
+7z x Bosphorus_3840x2160_120fps_420_8bit_YUV_Y4M.7z
+
+echo "#!/bin/sh
+
+if [ \"\$NUM_CPU_CORES\" -gt 64 ]; then
+	NUM_CPU_CORES=64
+fi
+
+./aomenc.exe --threads=\$NUM_CPU_CORES -o test.av1 \$@ > 1.log 2>&1
+echo \$? > ~/test-exit-status
+sed \$'s/[^[:print:]\t]/\\n/g' 1.log > \$LOG_FILE
+rm -f test.av1" > aom-av1
+chmod +x aom-av1

ob-cache/test-profiles/pts/aom-av1-2.4.0/results-definition.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.4.0m1-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Pass 1/2 frame    3/4        768B    2048b/f   61440b/s  165907 us #_RESULT_# fps)</OutputTemplate>
+    <LineHint>fps</LineHint>
+    <TurnCharsToSpace>(</TurnCharsToSpace>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/aom-av1-2.4.0/test-definition.xml

@@ -0,0 +1,75 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.4.0m1-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>AOM AV1</Title>
+    <AppVersion>3.1</AppVersion>
+    <Description>This is a test of the AOMedia AV1 encoder (libaom) developed by AOMedia and Google.</Description>
+    <ResultScale>Frames Per Second</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>2.4.0</Version>
+    <SupportedPlatforms>Linux, MacOSX, BSD, Windows</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>Processor</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>build-utilities, p7zip, cmake, perl, yasm</ExternalDependencies>
+    <EnvironmentSize>1950</EnvironmentSize>
+    <ProjectURL>https://aomedia.googlesource.com/aom/</ProjectURL>
+    <InternalTags>SMP</InternalTags>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Default>
+      <Arguments>--tile-columns=2 --tile-rows=2 --row-mt=1</Arguments>
+    </Default>
+    <Option>
+      <DisplayName>Encoder Mode</DisplayName>
+      <Identifier>enc-mode</Identifier>
+      <Menu>
+        <Entry>
+          <Name>Speed 9 Realtime</Name>
+          <Value>--cpu-used=9 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 8 Realtime</Name>
+          <Value>--cpu-used=8 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 6 Realtime</Name>
+          <Value>--cpu-used=6 --rt</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 6 Two-Pass</Name>
+          <Value>--cpu-used=6</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 4 Two-Pass</Name>
+          <Value>--cpu-used=4</Value>
+        </Entry>
+        <Entry>
+          <Name>Speed 0 Two-Pass</Name>
+          <Value>--cpu-used=0 --limit=20</Value>
+          <Message>Slowest</Message>
+        </Entry>
+      </Menu>
+    </Option>
+    <Option>
+      <DisplayName>Input</DisplayName>
+      <Identifier>input</Identifier>
+      <Menu>
+        <Entry>
+          <Name>Bosphorus 1080p</Name>
+          <Value>Bosphorus_1920x1080_120fps_420_8bit_YUV.y4m</Value>
+        </Entry>
+        <Entry>
+          <Name>Bosphorus 4K</Name>
+          <Value>Bosphorus_3840x2160.y4m</Value>
+        </Entry>
+      </Menu>
+    </Option>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/apache-siege-1.0.5/downloads.xml

@@ -0,0 +1,53 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.0m2-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://archive.apache.org/dist/httpd/httpd-2.4.29.tar.bz2, http://ftp.lfs-matrix.net/pub/blfs/conglomeration/httpd/httpd-2.4.29.tar.bz2</URL>
+      <MD5>0c599404ef6b69eee95bcd9fcd094407</MD5>
+      <SHA256>777753a5a25568a2a27428b2214980564bc1c38c1abf9ccc7630b639991f7f00</SHA256>
+      <FileName>httpd-2.4.29.tar.bz2</FileName>
+      <FileSize>6567926</FileSize>
+      <PlatformSpecific>Linux, Solaris, BSD, MacOSX</PlatformSpecific>
+    </Package>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/apache-ab-test-files-1.tar.gz, http://www.phoronix.net/downloads/phoronix-test-suite/benchmark-files/apache-ab-test-files-1.tar.gz</URL>
+      <MD5>ca0c5bf0dd482a2847c68a52c0759942</MD5>
+      <FileName>apache-ab-test-files-1.tar.gz</FileName>
+      <FileSize>6008</FileSize>
+    </Package>
+    <Package>
+      <URL>http://archive.apache.org/dist/apr/apr-1.6.3.tar.bz2</URL>
+      <MD5>12f2a349483ad6f12db49ba01fbfdbfa</MD5>
+      <SHA256>131f06d16d7aabd097fa992a33eec2b6af3962f93e6d570a9bd4d85e95993172</SHA256>
+      <FileName>apr-1.6.3.tar.bz2</FileName>
+      <FileSize>854100</FileSize>
+      <PlatformSpecific>Linux, Solaris, BSD, MacOSX</PlatformSpecific>
+    </Package>
+    <Package>
+      <URL>http://www.apache.org/dist/apr/apr-util-1.6.1.tar.bz2, http://apache.cs.utah.edu//apr/apr-util-1.6.1.tar.bz2</URL>
+      <MD5>8ff5dc36fa39a2a3db1df196d3ed6086</MD5>
+      <SHA256>d3e12f7b6ad12687572a3a39475545a072608f4ba03a6ce8a3778f607dd0035b</SHA256>
+      <FileName>apr-util-1.6.1.tar.bz2</FileName>
+      <FileSize>428595</FileSize>
+      <PlatformSpecific>Linux, Solaris, BSD, MacOSX</PlatformSpecific>
+    </Package>
+    <Package>
+      <URL>http://download.joedog.org/siege/siege-3.1.4.tar.gz</URL>
+      <MD5>a893b92a453e1c1d596314aa951981f4</MD5>
+      <SHA256>0436970ca81ade76eb419bc42d3f8460b475079eb5d8f199d2fa83328893099d</SHA256>
+      <FileName>siege-3.1.4.tar.gz</FileName>
+      <FileSize>530149</FileSize>
+      <PlatformSpecific>Linux, Solaris, BSD, MacOSX</PlatformSpecific>
+    </Package>
+    <Package>
+      <URL>https://raw.githubusercontent.com/apurvanandan1997/pts-test-profiles-patches/master/apache-siege-1.0.4/INCLUDE-SIGNAL-HEADER.patch</URL>
+      <MD5>0d3415820c82fbebbfe571c339d0badd</MD5>
+      <SHA256>67dcc5efaf079e9725a4350c3f760b69ca7a37dd04766ab92b005976e064f70b</SHA256>
+      <FileName>INCLUDE-SIGNAL-HEADER.patch</FileName>
+      <FileSize>260</FileSize>
+      <PlatformSpecific>BSD</PlatformSpecific>
+      <Optional>TRUE</Optional>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/apache-siege-1.0.5/install.sh

@@ -0,0 +1,44 @@
+#!/bin/sh
+
+mkdir $HOME/httpd_
+
+tar -zxvf apache-ab-test-files-1.tar.gz
+tar -jxvf httpd-2.4.29.tar.bz2
+tar -jxvf apr-util-1.6.1.tar.bz2
+tar -jxvf apr-1.6.3.tar.bz2
+mv apr-1.6.3 httpd-2.4.29/srclib/apr
+mv apr-util-1.6.1 httpd-2.4.29/srclib/apr-util
+
+cd httpd-2.4.29/
+./configure --prefix=$HOME/httpd_ --with-included-apr
+make -j $NUM_CPU_CORES
+echo $? > ~/install-exit-status
+make install
+cd ~
+rm -rf httpd-2.4.29/
+rm -rf httpd_/manual/
+
+patch -p0 < CHANGE-APACHE-PORT.patch
+mv -f test.html httpd_/htdocs/
+mv -f pts.png httpd_/htdocs/
+
+
+cd ~
+tar -xf siege-3.1.4.tar.gz
+if [ $OS_TYPE = "BSD" ]
+then
+        patch -p0 < INCLUDE-SIGNAL-HEADER.patch
+fi
+cd siege-3.1.4
+./configure
+make -j $NUM_CPU_CORES
+cd utils
+bash siege.config
+cd ~
+
+echo "#!/bin/sh
+cd siege-3.1.4/src
+./siege \$@ 2>&1 | grep -v HTTP > \$LOG_FILE
+echo \$? > ~/test-exit-status" > apache-siege
+
+chmod +x apache-siege

ob-cache/test-profiles/pts/apache-siege-1.0.5/post.sh

@@ -0,0 +1,4 @@
+#!/bin/sh
+./httpd_/bin/apachectl -k stop
+rm -f httpd_/logs/*
+sleep 3

ob-cache/test-profiles/pts/apache-siege-1.0.5/pre.sh

@@ -0,0 +1,7 @@
+#!/bin/sh
+./httpd_/bin/apachectl -k start -f $HOME/httpd_/conf/httpd.conf
+sleep 5
+
+cd siege-3.1.4/utils
+bash siege.config
+cd ~

ob-cache/test-profiles/pts/apache-siege-1.0.5/results-definition.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.0m2-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Transaction rate:	    #_RESULT_# trans/sec</OutputTemplate>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/apache-siege-1.0.5/test-definition.xml

@@ -0,0 +1,66 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.0m2-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>Apache Siege</Title>
+    <AppVersion>2.4.29</AppVersion>
+    <Description>This is a test of the Apache web server performance being facilitated by the Siege web server benchmark program.</Description>
+    <ResultScale>Transactions Per Second</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>1.0.5</Version>
+    <SupportedPlatforms>Linux, Solaris, BSD, MacOSX</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>System</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>build-utilities, perl, pcre, openssl-development, expat</ExternalDependencies>
+    <EnvironmentSize>208</EnvironmentSize>
+    <ProjectURL>https://www.joedog.org/siege-home/</ProjectURL>
+    <InternalTags>SMP</InternalTags>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Default>
+      <Arguments>-r10000 -d1 -b </Arguments>
+      <PostArguments> http://localhost:8088/test.html</PostArguments>
+    </Default>
+    <Option>
+      <DisplayName>Concurrent Users</DisplayName>
+      <Identifier>concurrent</Identifier>
+      <ArgumentPrefix>-c</ArgumentPrefix>
+      <Menu>
+        <Entry>
+          <Name>1</Name>
+          <Value>1</Value>
+        </Entry>
+        <Entry>
+          <Name>10</Name>
+          <Value>10</Value>
+        </Entry>
+        <Entry>
+          <Name>50</Name>
+          <Value>50</Value>
+        </Entry>
+        <Entry>
+          <Name>100</Name>
+          <Value>100</Value>
+        </Entry>
+        <Entry>
+          <Name>200</Name>
+          <Value>200</Value>
+        </Entry>
+        <Entry>
+          <Name>250</Name>
+          <Value>250</Value>
+        </Entry>
+        <Entry>
+          <Name>500</Name>
+          <Value>500</Value>
+        </Entry>
+      </Menu>
+    </Option>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/apitest-1.1.1/downloads.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.0m2-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://phoronix-test-suite.com/benchmark-files/apitest-20140726.tar.bz2</URL>
+      <MD5>28ac817817d35ab335ad40dcec682b6d</MD5>
+      <SHA256>67a48803c10c147f99632e1aa54cf1afce1b785d2ecf850b5f960e72d2dd5258</SHA256>
+      <FileName>apitest-20140726.tar.bz2</FileName>
+      <FileSize>23855194</FileSize>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/apitest-1.1.1/install.sh

@@ -0,0 +1,16 @@
+#!/bin/sh
+
+tar -xjf apitest-20140726.tar.bz2
+cd apitest-master
+mkdir out
+cd out
+cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release -DHAVE_LIBUDEV_H=0  ..
+make -j $NUM_CPU_JOBS
+echo $? > ~/install-exit-status
+
+cd ~
+echo "#!/bin/sh
+cd apitest-master/bin/
+./apitest \$@ > \$LOG_FILE 2>&1
+echo $? > ~/test-exit-status" > apitest
+chmod +x apitest

ob-cache/test-profiles/pts/apitest-1.1.1/results-definition.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.0m2-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate> NullProblem             oglcore    NullSolution                     30316       15.000     #_RESULT_#        0.495</OutputTemplate>
+    <LineBeforeHint>fps</LineBeforeHint>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/apitest-1.1.1/test-definition.xml

@@ -0,0 +1,136 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.0m2-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>APITest</Title>
+    <AppVersion>2014-07-26</AppVersion>
+    <Description>APITest is a micro-benchmark developed by John McDonald of OpenGL 4 functionality.</Description>
+    <ResultScale>Frames Per Second</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>1.1.1</Version>
+    <SupportedPlatforms>Linux, MacOSX</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>Graphics</TestType>
+    <License>Free</License>
+    <Status>Deprecated</Status>
+    <ExternalDependencies>build-utilities, sdl2-development, cmake</ExternalDependencies>
+    <RequiresDisplay>TRUE</RequiresDisplay>
+    <EnvironmentSize>225</EnvironmentSize>
+    <ProjectURL>http://github.com/nvMcJohn/apitest</ProjectURL>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Default>
+      <Arguments>-b -t 10 -a oglcore</Arguments>
+    </Default>
+    <Option>
+      <DisplayName>Resolution</DisplayName>
+      <Identifier>auto-resolution</Identifier>
+      <ArgumentPrefix>-r </ArgumentPrefix>
+      <Menu>
+        <Entry>
+          <Name>$VIDEO_WIDTH x $VIDEO_HEIGHT</Name>
+          <Value>$VIDEO_WIDTH $VIDEO_HEIGHT</Value>
+        </Entry>
+      </Menu>
+    </Option>
+    <Option>
+      <DisplayName>Test</DisplayName>
+      <Identifier>test</Identifier>
+      <ArgumentPrefix>-s </ArgumentPrefix>
+      <Menu>
+        <Entry>
+          <Name>DynamicStreaming GLBufferSubData</Name>
+          <Value>GLBufferSubData</Value>
+        </Entry>
+        <Entry>
+          <Name>DynamicStreaming GLMapUnsynchronized</Name>
+          <Value>GLMapUnsynchronized</Value>
+        </Entry>
+        <Entry>
+          <Name>DynamicStreaming GLMapPersistent</Name>
+          <Value>GLMapPersistent</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLUniform</Name>
+          <Value>GLUniform</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLDrawLoop</Name>
+          <Value>GLDrawLoop</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLMultiDrawBuffer-SDP</Name>
+          <Value>GLMultiDrawBuffer-SDP</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLMultiDrawBuffer-NoSDP</Name>
+          <Value>GLMultiDrawBuffer-NoSDP</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLBufferRange</Name>
+          <Value>GLBufferRange</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLBufferSubData</Name>
+          <Value>GLBufferSubData</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLBufferStorage-SDP</Name>
+          <Value>GLBufferStorage-SDP</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLBufferStorage-NoSDP</Name>
+          <Value>GLBufferStorage-NoSDP</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLDynamicBuffer</Name>
+          <Value>GLDynamicBuffer</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLMapUnsynchronized</Name>
+          <Value>GLMapUnsynchronized</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLMapPersistent</Name>
+          <Value>GLMapPersistent</Value>
+        </Entry>
+        <Entry>
+          <Name>UntexturedObjects GLTexCoord</Name>
+          <Value>GLTexCoord</Value>
+        </Entry>
+        <Entry>
+          <Name>TexturedQuadsProblem GLBindless</Name>
+          <Value>GLBindless</Value>
+        </Entry>
+        <Entry>
+          <Name>TexturedQuadsProblem GLNaive</Name>
+          <Value>GLNaive</Value>
+        </Entry>
+        <Entry>
+          <Name>TexturedQuadsProblem GLNaiveUniform</Name>
+          <Value>GLNaiveUniform</Value>
+        </Entry>
+        <Entry>
+          <Name>TexturedQuadsProblem GLNoTex</Name>
+          <Value>GLNoTex</Value>
+        </Entry>
+        <Entry>
+          <Name>TexturedQuadsProblem GLNoTexUniform</Name>
+          <Value>GLNoTexUniform</Value>
+        </Entry>
+        <Entry>
+          <Name>TexturedQuadsProblem GLSBTA</Name>
+          <Value>GLSBTA</Value>
+        </Entry>
+        <Entry>
+          <Name>TexturedQuadsProblem GLTextureArray</Name>
+          <Value>GLTextureArray</Value>
+        </Entry>
+      </Menu>
+    </Option>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/apitrace-1.0.2/downloads.xml

@@ -0,0 +1,17 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v8.0.0m2-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/apitrace-apitrace-3.0-0-gde9f3e5.zip</URL>
+      <MD5>9ef70fa990f165e30a4408762fdb4a76</MD5>
+      <FileSize>1279634</FileSize>
+    </Package>
+    <Package>
+      <URL></URL>
+      <MD5>21708bcee9c1e539b051779a76cc8880</MD5>
+      <FileName>redeclipse-1-trace.7z</FileName>
+      <FileSize>156191890</FileSize>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/apitrace-1.0.2/install.sh

@@ -0,0 +1,21 @@
+#!/bin/sh
+
+unzip -o apitrace-apitrace-3.0-0-gde9f3e5.zip
+7za -y x redeclipse-1-trace.7z
+
+rm -rf apitrace_
+mv -T apitrace-apitrace-de9f3e5 apitrace_
+cd apitrace_/
+cmake -H. -Bbuild
+make -C build
+echo $? > ~/install-exit-status
+
+# extend this test profile for image quality comparison, i.e.
+# glretrace -s dump/ -S 1600000-3613127/frame ../../redeclipse-1.trace 
+
+cd ~/
+echo "#!/bin/sh
+cd apitrace_/build/
+./glretrace -b ~/\$@ > \$LOG_FILE 2>&1
+echo $? > ~/test-exit-status" > apitrace
+chmod +x apitrace

ob-cache/test-profiles/pts/apitrace-1.0.2/results-definition.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v8.0.0m2-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Rendered 1966 frames in 93.4417 secs, average of #_RESULT_# fps</OutputTemplate>
+    <LineHint>fps</LineHint>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/apitrace-1.0.2/test-definition.xml

@@ -0,0 +1,41 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v8.0.0m2-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>APITrace</Title>
+    <AppVersion>3.0</AppVersion>
+    <Description>This is a benchmark measuring the performance of various OpenGL Linux games that lack suitable benchmarking modes so this is solely measuring the performance of pushing pre-recorded OpenGL calls as recorded by APITrace through the system's graphics driver stack and being executed on the GPU. This isn't measuring the system's performance in that game but rather just the recorded OpenGL performance being executed.</Description>
+    <ResultScale>Frames Per Second</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>1.0.2</Version>
+    <SupportedPlatforms>Linux</SupportedPlatforms>
+    <SoftwareType>Game</SoftwareType>
+    <TestType>Graphics</TestType>
+    <License>Free</License>
+    <Status>Deprecated</Status>
+    <SupportedArchitectures>x86, x86_64</SupportedArchitectures>
+    <ExternalDependencies>32bit-compatibility, cmake, python, build-utilities, p7zip</ExternalDependencies>
+    <EnvironmentSize>2000</EnvironmentSize>
+    <ProjectURL>http://github.com/apitrace/apitrace/</ProjectURL>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Option>
+      <DisplayName>Trace</DisplayName>
+      <Identifier>trace</Identifier>
+      <ArgumentPrefix></ArgumentPrefix>
+      <ArgumentPostfix></ArgumentPostfix>
+      <DefaultEntry>0</DefaultEntry>
+      <Menu>
+        <Entry>
+          <Name>Red Eclipse 1.2</Name>
+          <Value>redeclipse-1.trace</Value>
+          <Message></Message>
+        </Entry>
+      </Menu>
+    </Option>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/askap-2.1.0/downloads.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.0-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>https://github.com/ATNF/askap-benchmarks/archive/v1.0.tar.gz</URL>
+      <MD5>4155097c3b7f32002f97be4abf078bb9</MD5>
+      <SHA256>25ec60886de40d27c6100324224c724b3a0d3847d1f619f8aab45866d9cf857b</SHA256>
+      <FileName>askap-benchmarks-1.0.tar.gz</FileName>
+      <FileSize>129002812</FileSize>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/askap-2.1.0/install.sh

@@ -0,0 +1,53 @@
+#!/bin/sh
+
+tar -xf askap-benchmarks-1.0.tar.gz
+
+cd ~/askap-benchmarks-1.0/attic/tConvolveOpenCL/
+make
+cd ~/askap-benchmarks-1.0/attic/tConvolveCuda
+make
+cd ~/askap-benchmarks-1.0/current/tConvolveMPI
+sed -i 's/CXX=CC/CXX=mpic++/g' Makefile
+make
+cd ~/askap-benchmarks-1.0/attic/tConvolveOMP
+make
+cd ~/askap-benchmarks-1.0/attic/tConvolveMT
+make
+cd ~/askap-benchmarks-1.0/current/tHogbomCleanOMP
+cp ../../data/dirty_4096.img dirty.img
+cp ../../data/psf_4096.img psf.img
+make
+echo $? > ~/install-exit-status
+
+cd ~/
+echo "#!/bin/sh
+cd askap-benchmarks-1.0/
+
+case \"\$1\" in
+\"tConvolveOpenCL\")
+	cd attic/tConvolveOpenCL
+	./tConvolveOpenCL > \$LOG_FILE
+	;;
+\"tConvolveCuda\")
+	cd attic/tConvolveCuda
+	./tConvolveCuda > \$LOG_FILE
+	;;
+\"tConvolveMPI\")
+	cd current/tConvolveMPI
+	mpirun --allow-run-as-root -np \$NUM_CPU_PHYSICAL_CORES ./tConvolveMPI > \$LOG_FILE
+	;;
+\"tConvolveOMP\")
+	cd attic/tConvolveOMP
+	OMP_NUM_THREADS=\$NUM_CPU_CORES ./tConvolveOMP > \$LOG_FILE
+	;;
+\"tConvolveMT\")
+	cd attic/tConvolveMT
+	./tConvolveMT \$NUM_CPU_CORES > \$LOG_FILE
+	;;
+\"tHogbomCleanOMP\")
+	cd current/tHogbomCleanOMP
+	./tHogbomCleanOMP > \$LOG_FILE
+	;;
+esac
+echo \$? > ~/test-exit-status" > askap
+chmod +x askap

ob-cache/test-profiles/pts/askap-2.1.0/results-definition.xml

@@ -0,0 +1,30 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.0-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Gridding rate   #_RESULT_#</OutputTemplate>
+    <ResultScale>Million Grid Points Per Second</ResultScale>
+    <AppendToArgumentsDescription>Gridding</AppendToArgumentsDescription>
+  </ResultsParser>
+  <ResultsParser>
+    <OutputTemplate>Degridding rate   #_RESULT_#</OutputTemplate>
+    <ResultScale>Million Grid Points Per Second</ResultScale>
+    <AppendToArgumentsDescription>Degridding</AppendToArgumentsDescription>
+  </ResultsParser>
+  <ResultsParser>
+    <OutputTemplate>    Degridding rate (total)    #_RESULT_# (Mpix/sec)</OutputTemplate>
+    <LineHint>Degridding rate (total)</LineHint>
+    <ResultScale>Mpix/sec</ResultScale>
+    <AppendToArgumentsDescription>Degridding</AppendToArgumentsDescription>
+  </ResultsParser>
+  <ResultsParser>
+    <OutputTemplate>    Gridding rate (total)      #_RESULT_# (Mpix/sec)</OutputTemplate>
+    <LineHint>Gridding rate (total</LineHint>
+    <ResultScale>Mpix/sec</ResultScale>
+    <AppendToArgumentsDescription>Gridding</AppendToArgumentsDescription>
+  </ResultsParser>
+  <ResultsParser>
+    <OutputTemplate>    Cleaning rate  #_RESULT_# (iterations per second)</OutputTemplate>
+    <ResultScale>Iterations Per Second</ResultScale>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/askap-2.1.0/test-definition.xml

@@ -0,0 +1,57 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.2.0-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>ASKAP</Title>
+    <AppVersion>1.0</AppVersion>
+    <Description>ASKAP is a set of benchmarks from the Australian SKA Pathfinder. The principal ASKAP benchmarks are the Hogbom Clean Benchmark (tHogbomClean) and Convolutional Resamping Benchmark (tConvolve) as well as some previous ASKAP benchmarks being included as well for OpenCL and CUDA execution of tConvolve.</Description>
+    <ResultScale>Million Grid Points Per Second</ResultScale>
+    <Proportion>HIB</Proportion>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>2.1.0</Version>
+    <SupportedPlatforms>Linux</SupportedPlatforms>
+    <SoftwareType>Benchmark</SoftwareType>
+    <TestType>System</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <ExternalDependencies>build-utilities, cuda, opencl, openmpi-development</ExternalDependencies>
+    <EnvironmentSize>417</EnvironmentSize>
+    <ProjectURL>https://github.com/ATNF/askap-benchmarks</ProjectURL>
+    <InternalTags>CUDA, SMP, MPI, OpenMP</InternalTags>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+  <TestSettings>
+    <Option>
+      <DisplayName>Test</DisplayName>
+      <Identifier>test</Identifier>
+      <Menu>
+        <Entry>
+          <Name>tConvolve OpenCL</Name>
+          <Value>tConvolve OpenCL</Value>
+        </Entry>
+        <Entry>
+          <Name>tConvolve CUDA</Name>
+          <Value>tConvolveCuda</Value>
+        </Entry>
+        <Entry>
+          <Name>tConvolve MPI</Name>
+          <Value>tConvolveMPI</Value>
+        </Entry>
+        <Entry>
+          <Name>tConvolve OpenMP</Name>
+          <Value>tConvolveOMP</Value>
+        </Entry>
+        <Entry>
+          <Name>tConvolve MT</Name>
+          <Value>tConvolveMT</Value>
+        </Entry>
+        <Entry>
+          <Name>Hogbom Clean OpenMP</Name>
+          <Value>tHogbomCleanOMP</Value>
+        </Entry>
+      </Menu>
+    </Option>
+  </TestSettings>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/asmfish-1.1.2/downloads.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.1-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://www.phoronix-test-suite.com/benchmark-files/asmFish-20180723.zip</URL>
+      <MD5>15c79b8378787f5fee0a37ccc22fe97f</MD5>
+      <SHA256>f03f6c037ad37cde553ffd02efb4643a43a71cbb4942c809aeb22db12cb1e0c1</SHA256>
+      <FileName>asmFish-20180723.zip</FileName>
+      <FileSize>2207999</FileSize>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/asmfish-1.1.2/install.sh

@@ -0,0 +1,16 @@
+#!/bin/sh
+
+unzip -o asmFish-20180723.zip
+cd asmFish-master
+chmod +x LinuxOS_binaries/*
+cd ~
+
+echo "#!/bin/sh
+cd asmFish-master
+if [ \$OS_ARCH = \"aarch64\" ]
+then
+	echo \"bench 1024 \$NUM_CPU_CORES 26\" | ./LinuxOS_binaries/armFishL_2018-07-23_v8 > \$LOG_FILE 2>&1
+else
+	echo \"bench 1024 \$NUM_CPU_CORES 26\" |  ./LinuxOS_binaries/asmFishL_2018-07-23_base > \$LOG_FILE 2>&1
+fi" > asmfish
+chmod +x asmfish

ob-cache/test-profiles/pts/asmfish-1.1.2/install_macosx.sh

@@ -0,0 +1,11 @@
+#!/bin/sh
+
+unzip -o asmFish-20180723.zip
+cd asmFish-master
+chmod +x MacOS_binaries/*
+cd ~
+
+echo "#!/bin/sh
+cd asmFish-master/MacOS_binaries
+echo \"bench 1024 \$NUM_CPU_CORES 26\" |  ./asmFishX_2018-07-23_base > \$LOG_FILE 2>&1" > asmfish
+chmod +x asmfish

ob-cache/test-profiles/pts/asmfish-1.1.2/install_windows.sh

@@ -0,0 +1,8 @@
+#!/bin/sh
+
+unzip -o asmFish-20180723.zip
+
+echo "#!/bin/sh
+cd asmFish-master/WindowsOS_binaries
+echo \"bench 1024 \$NUM_CPU_CORES 26\" |  ./asmFishW_2018-07-23_base.exe > \$LOG_FILE 2>&1" > asmfish
+chmod +x asmfish

ob-cache/test-profiles/pts/asmfish-1.1.2/results-definition.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.1-->
+<PhoronixTestSuite>
+  <ResultsParser>
+    <OutputTemplate>Nodes/second    : #_RESULT_#</OutputTemplate>
+  </ResultsParser>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/asmfish-1.1.2/test-definition.xml

@@ -0,0 +1,25 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v10.0.1-->
+<PhoronixTestSuite>
+  <TestInformation>
+    <Title>asmFish</Title>
+    <AppVersion>2018-07-23</AppVersion>
+    <Description>This is a test of asmFish, an advanced chess benchmark written in Assembly.</Description>
+    <ResultScale>Nodes/second</ResultScale>
+    <Proportion>HIB</Proportion>
+    <SubTitle>1024 Hash Memory, 26 Depth</SubTitle>
+    <TimesToRun>3</TimesToRun>
+  </TestInformation>
+  <TestProfile>
+    <Version>1.1.2</Version>
+    <SupportedPlatforms>Linux, Windows, MacOSX</SupportedPlatforms>
+    <SoftwareType>Utility</SoftwareType>
+    <TestType>Processor</TestType>
+    <License>Free</License>
+    <Status>Verified</Status>
+    <EnvironmentSize>5</EnvironmentSize>
+    <ProjectURL>https://github.com/lantonov/asmFish/</ProjectURL>
+    <InternalTags>SMP</InternalTags>
+    <Maintainer>Michael Larabel</Maintainer>
+  </TestProfile>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/astcenc-1.0.0/downloads.xml

@@ -0,0 +1,37 @@
+<?xml version="1.0"?>
+<!--Phoronix Test Suite v9.8.0-->
+<PhoronixTestSuite>
+  <Downloads>
+    <Package>
+      <URL>http://phoronix-test-suite.com/benchmark-files/png-samples-1.tar.xz</URL>
+      <MD5>3f928e4d08777e6e84c54202a00429de</MD5>
+      <SHA256>9810c8fd3afd35b4755c2a46f14fc66e2b9199c22e46a5946123c9250f2d1ccd</SHA256>
+      <FileName>png-samples-1.tar.xz</FileName>
+      <FileSize>58346628</FileSize>
+    </Package>
+    <Package>
+      <URL>https://github.com/ARM-software/astc-encoder/archive/2.0.tar.gz</URL>
+      <MD5>93562e3d6d709b2e62b404cbd4ddba3f</MD5>
+      <SHA256>f466c224ad6c0bb44401d77a05a3155cc9368df01a57b33ec242a1ea7240eefe</SHA256>
+      <FileName>astc-encoder-2.0.tar.gz</FileName>
+      <FileSize>29956405</FileSize>
+      <PlatformSpecific>Linux</PlatformSpecific>
+    </Package>
+    <Package>
+      <URL>https://github.com/ARM-software/astc-encoder/releases/download/2.0/astcenc-2.0-macos-x64.zip</URL>
+      <MD5>7d44922e73ddd8bb51e9ef4e294bdca0</MD5>
+      <SHA256>79333ca74b9bf091c87ab290ad2c99ff002b8bab23dd8c0815687a5f65fc05f0</SHA256>
+      <FileName>astcenc-2.0-macos-x64.zip</FileName>
+      <FileSize>801491</FileSize>
+      <PlatformSpecific>MacOSX</PlatformSpecific>
+    </Package>
+    <Package>
+      <URL>https://github.com/ARM-software/astc-encoder/releases/download/2.0/astcenc-2.0-windows-x64.zip</URL>
+      <MD5>27ae2a95633a967ec2672d98cb389f29</MD5>
+      <SHA256>8db18954950b01f9a16c54a3c63afc6763692db7b96492330a9b726cdfebb7d0</SHA256>
+      <FileName>astcenc-2.0-windows-x64.zip</FileName>
+      <FileSize>1396420</FileSize>
+      <PlatformSpecific>Windows</PlatformSpecific>
+    </Package>
+  </Downloads>
+</PhoronixTestSuite>

ob-cache/test-profiles/pts/astcenc-1.0.0/install.sh

@@ -0,0 +1,13 @@
+#!/bin/sh
+
+tar -xf png-samples-1.tar.xz
+tar -xf astc-encoder-2.0.tar.gz
+cd astc-encoder-2.0/Source
+make -j $NUM_CPU_CORES
+echo \$? > ~/install-exit-status
+
+cd ~
+echo "#!/bin/sh
+./astc-encoder-2.0/Source/astcenc-avx2 -tl sample-4.png 1.png 8x6 \$@ > \$LOG_FILE 2>&1
+echo \$? > ~/test-exit-status" > astcenc
+chmod +x astcenc

ob-cache/test-profiles/pts/astcenc-1.0.0/install_macosx.sh

@@ -0,0 +1,10 @@
+#!/bin/sh
+
+tar -xf png-samples-1.tar.xz
+unzip -o astcenc-2.0-macos-x64.zip
+chmod +x astcenc-2.0-macos-x64/astcenc-avx2
+
+echo "#!/bin/sh
+./astcenc-2.0-macos-x64/astcenc-avx2 -tl sample-4.png 1.png 8x6 \$@ > \$LOG_FILE 2>&1
+echo \$? > ~/test-exit-status" > basis
+chmod +x basis