Results 1 to 9 of 9

Thread: Phoronix Test Suite 1.2.0 Beta 1

  1. #1
    Join Date
    Jan 2007
    Posts
    14,904

    Default Phoronix Test Suite 1.2.0 Beta 1

    Phoronix: Phoronix Test Suite 1.2.0 Beta 1

    Two months after shipping Phoronix Test Suite 1.0, we're announcing the first beta release for Phoronix Test Suite 1.2. This release incorporates many changes and new features, in fact too many to go over in a single article...

    http://www.phoronix.com/vr.php?view=NjY0MQ

  2. #2

    Default

    Also check out the new resolution detector option in there too

  3. #3
    Join Date
    Nov 2007
    Posts
    20

    Default

    Nice work Michael (and others), this is an impressive change-log.

    I found a small fix again

    This time regarding to monitoring voltages.
    File: system_monitor.php
    Code:
    if(in_array("v3.voltage", $to_show) || $monitor_voltage)
    		{
    			define("MONITOR_V3_VOLTAGE", 1);
    			pts_module::save_file(".s/BATTERY_POWER");
    		}
    should be

    Code:
    if(in_array("v3.voltage", $to_show) || $monitor_voltage)
    		{
    			define("MONITOR_V3_VOLTAGE", 1);
    			pts_module::save_file(".s/V3_VOLTAGE");
    		}
    in order to work probably.

    My ideas for a future release:

    when viewing results for monitoring in a web browser, maybe

    * add a legend for MIN/MAX/AVERAGE values

    * put something like "Elapsed Time: x min/hrs" under the diagram

    and some hints for other users setting up their sensors3.conf:
    (works with version 1.0.5 and 1.2.0b1)

    set your labels for
    * +3.33V to "V3.3"
    * +5.00V to "V5"
    * +12.00V to "V12"
    and the corresponding labels for temperatures to
    * "CPU Temp"
    * "Board Temp"

    whether it works or not, you can check easyly with

    Code:
    phoronix-test-suite sensors
    (ver. 1.0.5)

    for version 1.2.0b1 this was dropped, seems the docs need some small updates, too.

  4. #4

    Default

    Quote Originally Posted by Marox View Post
    Nice work Michael (and others), this is an impressive change-log.

    I found a small fix again

    This time regarding to monitoring voltages.
    File: system_monitor.php
    Code:
    if(in_array("v3.voltage", $to_show) || $monitor_voltage)
            {
                define("MONITOR_V3_VOLTAGE", 1);
                pts_module::save_file(".s/BATTERY_POWER");
            }
    should be

    Code:
    if(in_array("v3.voltage", $to_show) || $monitor_voltage)
            {
                define("MONITOR_V3_VOLTAGE", 1);
                pts_module::save_file(".s/V3_VOLTAGE");
            }
    in order to work probably.
    Thanks, should be fixed in git.


    Quote Originally Posted by Marox View Post
    My ideas for a future release:

    when viewing results for monitoring in a web browser, maybe

    * add a legend for MIN/MAX/AVERAGE values

    * put something like "Elapsed Time: x min/hrs" under the diagram
    Thanks for the feedback, I may incorporate some of this into the next beta.

    Quote Originally Posted by Marox View Post
    for version 1.2.0b1 this was dropped, seems the docs need some small updates, too.
    Where isn't this reflected in the docs? I thought I had updated them all.

  5. #5
    Join Date
    Nov 2007
    Posts
    20

    Default

    Where isn't this reflected in the docs? I thought I had updated them all.
    The corresponding passage is:
    The full list of supported sensor options can be found by running phoronix-test-suite module-info system_monitor. The sensors actually detected on the current system and their values can be read by running phoronix-test-suite sensors.
    (from sensor_monitoring.html in the .deb (1.2.0b1)

    Code:
    phoronix-test-suite sensors
    
    This option was dropped from the Phoronix Test Suite. For more information and the replacement option, view the latest documentation.
    so is there a new command, to check which / whether sensors are detected ?

  6. #6

    Default

    Quote Originally Posted by Marox View Post
    The corresponding passage is:
    (from sensor_monitoring.html in the .deb (1.2.0b1)

    Code:
    phoronix-test-suite sensors
    
    This option was dropped from the Phoronix Test Suite. For more information and the replacement option, view the latest documentation.
    so is there a new command, to check which / whether sensors are detected ?
    Oops, I'll get that corrected.

    Regarding a new command, I have an idea for one that just came to mind... Will probably write it up tonight. I am thinking it will be:

    phoronix-test-suite test-module system_monitor

  7. #7

    Default

    Quote Originally Posted by Marox View Post
    so is there a new command, to check which / whether sensors are detected ?
    With git, use debug-module:

    $ MONITOR=all ./phoronix-test-suite debug-module system_monitor

    ====================================
    Starting Module Test Process
    ====================================

    Calling: __startup()
    Calling: __pre_install_process()
    Calling: __pre_test_install()
    Calling: __post_test_install()
    Calling: __post_install_process()
    Calling: __pre_run_process()
    Calling: __pre_test_run()
    Calling: __interim_test_run()
    Calling: __post_test_run()
    Calling: __post_run_process()
    Calling: __shutdown()

    ====================================
    Current Sensor Readings:

    GPU Thermal Monitor: 58 C
    CPU Thermal Monitor: 49 C
    System Thermal Monitor: 39 C
    CPU Frequency Monitor: 2501.00 MHz
    GPU Frequency Monitor: 400 MHz
    CPU Usage Monitor: 15.60 Percent
    ====================================
    Or to have a bit less output, use test-module:

    $ MONITOR=all ./phoronix-test-suite test-module system_monitor

    ====================================
    Starting Module Test Process
    ====================================


    ====================================
    Current Sensor Readings:

    GPU Thermal Monitor: 58 C
    CPU Thermal Monitor: 51 C
    System Thermal Monitor: 41 C
    CPU Frequency Monitor: 2501.00 MHz
    GPU Frequency Monitor: 400 MHz
    CPU Usage Monitor: 9.22 Percent
    ====================================
    This also provides a way for developers to test modules

  8. #8
    Join Date
    Nov 2007
    Posts
    20

    Default

    While monitoring sensors works fine, at least for me, i couldn't pass the compliance-sensors test. So i looked up the corresponding scripts and found some inconsistences.

    for monitoring temperatures and voltages we use:
    File: pts-functions_system.php

    Code:
    function system_line_voltage($type)
    {
        if($type == "CPU")
            $voltage = read_sensors("VCore");
        else if($type == "V3")
            $voltage = read_sensors("V3.3");
        else if($type == "V5")
            $voltage = read_sensors("V5");
        else if($type == "V12")
            $voltage = read_sensors("V12");
        ...
        ...
    and
    Code:
    function system_temperature()
    {
        $temp_c = read_sensors("Sys Temp");
    
        if(empty($temp_c))
            $temp_c = read_sensors("Board Temp");
        ...
        ...
    when running
    Code:
     phoronix-test-suite run compliance-sensors
    we check against different strings:
    File: sensors-check
    Code:
    array_push($sensors, read_sensors("VCore"));
    array_push($sensors, read_sensors("+3.3V"));
    array_push($sensors, read_sensors("+5V"));
    array_push($sensors, read_sensors("+12V"));
    and

    Code:
    $sys_temp = read_sensors("Sys Temp");
    if(empty($sys_temp))
    	$sys_temp = read_sensors("temp2");
    array_push($sensors, $sys_temp);
    So strings for voltages are different and a check to include "Board Temp" is missing.

    Marox

  9. #9

    Default

    Thanks, in git master this should be improved.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •