Announcement

Collapse
No announcement yet.

Phoronix Test Suite 1.0.3 Released

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Phoronix Test Suite 1.0.3 Released

    Phoronix: Phoronix Test Suite 1.0.3 Released

    It's been about two weeks since the release of Phoronix Test Suite 1.0.2, and now version 1.0.3 has been released. This minor update to this Linux benchmarking and testing platform licensed under the GNU GPLv3 adds new test profiles, a new suite, and a couple fixes. The new test profiles in this release include byte, bonnie, and ut2004-demo...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    The bonnie test doesn't seem to work for me (openSUSE 11.0, x86):

    $ ./phoronix-test-suite run bonnie

    Would you like to save these test results (Y/n)? n

    Type:

    1: Sequential Create
    2: Sequential Read
    3: Sequential Delete
    4: Random Create
    5: Random Read
    6: Random Delete

    Please Enter Your Choice: 1

    ====================================
    Bonnie++ (Run 1 of 1)
    ====================================

    ./bonnie: line 5: ./bonnie_/sbin/bonnie++: No such file or directory
    PHP Notice: Undefined offset: 2 in /home/knuckles/pts/phoronix-test-suite/pts/test-resources/bonnie/parse-results.php on line 13

    ####################################
    Bonnie++:
    Sequential Create


    Average: 0.00 Operations / Second
    ####################################

    Comment


    • #3
      What was the output when running: phoronix-test-suite force-install bonnie
      Michael Larabel
      https://www.michaellarabel.com/

      Comment


      • #4
        The output I get is:

        ====================================
        Downloading Files For: bonnie
        Estimated Download Size: 0.1 MB
        ====================================



        Downloading File: bonnie++-1.03a.tgz

        --2008-07-10 14:12:18-- http://internap.dl.sourceforge.net/s...ie++-1.03a.tgz
        Resolving internap.dl.sourceforge.net... 70.42.27.131
        Connecting to internap.dl.sourceforge.net|70.42.27.131|:80... connected.
        HTTP request sent, awaiting response... 200 OK
        Length: 76207 (74K) [application/x-tar]
        Saving to: `bonnie++-1.03a.tgz'

        100%[================================================== ================================================>] 76,207 151K/s in 0.5s

        2008-07-10 14:12:20 (151 KB/s) - `bonnie++-1.03a.tgz' saved [76207/76207]


        ====================================
        Installing Benchmark: bonnie
        Estimated Install Size: 0.1 MB
        ====================================

        bonnie++.cpp:141: warning: unused parameter ‘sig’
        bonnie++.cpp:141: warning: unused parameter ‘unused’
        bonnie++.cpp: In function ‘int main(int, char**)’:
        bonnie++.cpp:287: warning: suggest a space before ‘;’ or explicit braces around empty body in ‘for’ statement
        bonnie++.cpp:366: warning: suggest a space before ‘;’ or explicit braces around empty body in ‘for’ statement
        zcav.cpp: In function ‘int main(int, char**)’:
        zcav.cpp:73: error: ‘strdup’ was not declared in this scope
        zcav.cpp:75: warning: suggest a space before ‘;’ or explicit braces around empty body in ‘for’ statement
        zcav.cpp:112: error: ‘strcmp’ was not declared in this scope
        make: *** [zcav] Error 1
        make: *** Waiting for unfinished jobs....
        zcav.cpp: In function ‘int main(int, char**)’:
        zcav.cpp:73: error: ‘strdup’ was not declared in this scope
        zcav.cpp:75: warning: suggest a space before ‘;’ or explicit braces around empty body in ‘for’ statement
        zcav.cpp:112: error: ‘strcmp’ was not declared in this scope
        make: *** [zcav] Error 1
        bonnie++-1.03a/
        bonnie++-1.03a/sun/
        bonnie++-1.03a/sun/Makefile
        bonnie++-1.03a/sun/pkginfo.in
        bonnie++-1.03a/sun/pkginfo
        bonnie++-1.03a/sun/prototype
        bonnie++-1.03a/semaphore.cpp
        bonnie++-1.03a/bon_suid.cpp
        bonnie++-1.03a/Makefile
        bonnie++-1.03a/bon_csv2html.1
        bonnie++-1.03a/bon_file.h
        bonnie++-1.03a/bon_csv2html.in
        bonnie++-1.03a/conf.h.in
        bonnie++-1.03a/bon_io.cpp
        bonnie++-1.03a/bonnie++.spec
        bonnie++-1.03a/configure
        bonnie++-1.03a/bon_csv2html
        bonnie++-1.03a/bon_csv2txt.in
        bonnie++-1.03a/bon_time.h
        bonnie++-1.03a/semaphore.h
        bonnie++-1.03a/configure.in
        bonnie++-1.03a/bonnie++.8
        bonnie++-1.03a/forkit.h
        bonnie++-1.03a/credits.txt
        bonnie++-1.03a/bonnie++.spec.in
        bonnie++-1.03a/install.sh
        bonnie++-1.03a/changelog.txt
        bonnie++-1.03a/bonnie++.cpp
        bonnie++-1.03a/forkit.cpp
        bonnie++-1.03a/zcav.cpp
        bonnie++-1.03a/port.h.in
        bonnie++-1.03a/debian/
        bonnie++-1.03a/debian/dirs
        bonnie++-1.03a/debian/docs
        bonnie++-1.03a/debian/control
        bonnie++-1.03a/debian/rules
        bonnie++-1.03a/debian/changelog
        bonnie++-1.03a/debian/copyright
        bonnie++-1.03a/conf.h
        bonnie++-1.03a/bon_file.cpp
        bonnie++-1.03a/Makefile.in
        bonnie++-1.03a/bon_csv2txt.1
        bonnie++-1.03a/bonnie.h.in
        bonnie++-1.03a/port.h
        bonnie++-1.03a/zcav.8
        bonnie++-1.03a/copyright.txt
        bonnie++-1.03a/sh.common
        bonnie++-1.03a/bon_io.h
        bonnie++-1.03a/bonnie.8
        bonnie++-1.03a/bonnie.h
        bonnie++-1.03a/bon_csv2txt
        bonnie++-1.03a/bon_time.cpp
        bonnie++-1.03a/readme.html
        checking for g++... g++
        checking for C++ compiler default output... a.out
        checking whether the C++ compiler works... yes
        checking whether we are cross compiling... no
        checking for suffix of executables...
        checking for suffix of object files... o
        checking whether we are using the GNU C++ compiler... yes
        checking whether g++ accepts -g... yes
        checking how to run the C++ preprocessor... g++ -E
        checking for a BSD-compatible install... /usr/bin/install -c
        checking for an ANSI C-conforming const... yes
        checking for egrep... grep -E
        checking for ANSI C header files... yes
        checking for sys/types.h... yes
        checking for sys/stat.h... yes
        checking for stdlib.h... yes
        checking for string.h... yes
        checking for memory.h... yes
        checking for strings.h... yes
        checking for inttypes.h... yes
        checking for stdint.h... yes
        checking for unistd.h... yes
        checking for size_t... yes
        checking vector.h usability... no
        checking vector.h presence... no
        checking for vector.h... no
        STL not installed so no ZCAV!
        checking vector usability... yes
        checking vector presence... yes
        checking for vector... yes
        checking algorithm usability... yes
        checking algorithm presence... yes
        checking for algorithm... yes
        checking algo.h usability... no
        checking algo.h presence... no
        checking for algo.h... no
        checking algo usability... no
        checking algo presence... no
        checking for algo... no
        configure: creating ./config.status
        config.status: creating Makefile
        config.status: creating bonnie.h
        config.status: creating port.h
        config.status: creating bonnie++.spec
        config.status: creating bon_csv2html
        config.status: creating bon_csv2txt
        config.status: creating sun/pkginfo
        config.status: creating conf.h
        g++ -O2 -DNDEBUG -Wall -W -Wshadow -Wpointer-arith -Wwrite-strings -pedantic -ffor-scope -c bon_io.cpp
        g++ -O2 -DNDEBUG -Wall -W -Wshadow -Wpointer-arith -Wwrite-strings -pedantic -ffor-scope -c bon_file.cpp
        g++ -O2 -DNDEBUG -Wall -W -Wshadow -Wpointer-arith -Wwrite-strings -pedantic -ffor-scope -c bon_time.cpp
        g++ -O2 -DNDEBUG -Wall -W -Wshadow -Wpointer-arith -Wwrite-strings -pedantic -ffor-scope -c semaphore.cpp
        g++ -O2 -DNDEBUG -Wall -W -Wshadow -Wpointer-arith -Wwrite-strings -pedantic -ffor-scope -c forkit.cpp
        g++ -O2 -DNDEBUG -Wall -W -Wshadow -Wpointer-arith -Wwrite-strings -pedantic -ffor-scope -c bon_suid.cpp
        g++ -O2 -DNDEBUG -Wall -W -Wshadow -Wpointer-arith -Wwrite-strings -pedantic -ffor-scope bonnie++.cpp -o bonnie++ bon_io.o bon_file.o bon_time.o semaphore.o forkit.o bon_suid.o
        g++ -O2 -DNDEBUG -Wall -W -Wshadow -Wpointer-arith -Wwrite-strings -pedantic -ffor-scope zcav.cpp -o zcav bon_suid.o
        g++ -O2 -DNDEBUG -Wall -W -Wshadow -Wpointer-arith -Wwrite-strings -pedantic -ffor-scope zcav.cpp -o zcav bon_suid.o

        And nothing more. (I checked and also there was no binary on the install directory)

        Comment


        • #5
          Bonnie++ needs to be patched to compile on GCC 4.3+.

          Comment


          • #6
            sad, sad, still(?) no fio-profile. did you take a look at it?
            io-performance is the most important performance-criteria which follows cpu/ram-performance...

            Comment


            • #7
              Originally posted by Regenwald View Post
              sad, sad, still(?) no fio-profile. did you take a look at it?
              io-performance is the most important performance-criteria which follows cpu/ram-performance...
              When did you mention that? I don't recall seeing any requests for it (best way is to create a new thread). Anyhow, in git master (for what will be Phoronix Test Suite 1.0.4) is now a profile called fio with the fio test profile. However, right now it's rather basic and just measures the total time to run fio. If you have extensive knowledge with fio, I'd gladly accept patches to extend its functionality of this profile.
              Michael Larabel
              https://www.michaellarabel.com/

              Comment


              • #8
                Discussion & collaboration on the Phoronix Test Suite software and specification.

                unfortunaly, i'm lacked of needed skills to write patches

                Comment


                • #9
                  Originally posted by Regenwald View Post
                  unfortunaly, i'm lacked of needed skills to write patches
                  Well, if you can then just tell me all the fio arguments you'd like and other specifics, I can write the patch.
                  Michael Larabel
                  https://www.michaellarabel.com/

                  Comment


                  • #10
                    well, i think this configuration (aka .fio-data) from this software presentation (http://www.linux.com/feature/131063) should do the beginning. it seems to create a heavy workload. unfortunatly, i don't know about io-specific functions. oh i just looked into the .tar.gz, there are already several exemples integrated, such as the intel file server acces pattern (official for workstation & fileservers), several client-server-network jobs and so on. some really exciting stuff
                    so my propose is to just take a look at it and think about it.
                    you can find the exemples in the "exemples"-dir in the tar.gz.

                    ps: did you read about this?

                    Comment

                    Working...
                    X