Announcement

Collapse
No announcement yet.

Difference between various names that I am prompted for.

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

  • Difference between various names that I am prompted for.

    When I run a test in phoronix, I am asked three questions.

    1. Enter a name to save these results under:
    2. Enger a unique name to describe this test run / configuration:
    3. If you wish, enter a new description below to better describe this result set / system configuration under test.

    What is the point of these three questions?
    How do my responses affect what happens upon upload to openbenchmarking.org?
    How can I save the results of several runs in one result set, for instance to see if system changes had an effect?

    Surprising that the documentation doesn't discuss this basic issue.

  • #2
    Originally posted by hnaparst View Post
    When I run a test in phoronix, I am asked three questions.

    1. Enter a name to save these results under:
    2. Enger a unique name to describe this test run / configuration:
    3. If you wish, enter a new description below to better describe this result set / system configuration under test.

    What is the point of these three questions?
    How do my responses affect what happens upon upload to openbenchmarking.org?
    How can I save the results of several runs in one result set, for instance to see if system changes had an effect?

    Surprising that the documentation doesn't discuss this basic issue.
    Code:
    1)        |   Big title showdown  |
    
              /                        \
    2)   AMD                          Intel
           |                               |
           V                               V
    
    3)  Underclocked               Overclocked
     Running of Battery            Running on flux capacitor
    Get the idea now? In order for both results to be put together in a comparison, 1) must be the same on both runs for them to merge.
    Last edited by deanjo; 11-21-2011, 08:59 PM.

    Comment


    • #3
      Thanks, that is clear.

      It is real genius of the developer to avoid writing documentation
      and to just have the users document all the features by trial and error
      in the forums. There was one problem that a user had recently,
      and the developer came to the forum and said that the user should
      just search the forums for the answer!

      Just sarcasm, of course. It is a terrible waste of everyone's time,
      shows disrespect for the users, and is very frustrating to have to
      devote between an hour and a week to the solution of problems
      that should be documented clearly.

      Comment


      • #4
        Originally posted by hnaparst View Post
        Thanks, that is clear.

        It is real genius of the developer to avoid writing documentation
        and to just have the users document all the features by trial and error
        in the forums. There was one problem that a user had recently,
        and the developer came to the forum and said that the user should
        just search the forums for the answer!

        Just sarcasm, of course. It is a terrible waste of everyone's time,
        shows disrespect for the users, and is very frustrating to have to
        devote between an hour and a week to the solution of problems
        that should be documented clearly.
        There is documentation, but it's impossible to cover 100% of possible user questions, etc. The Phoronix Test Suite is an open-source project, so you're welcome to contribute to the documentation (or any other areas) or sponsor such. I don't think any of my enterprise users have documentation complaints.
        Michael Larabel
        http://www.michaellarabel.com/

        Comment


        • #5
          The documentation I see is http://www.phoronix-test-suite.com/?k=documentation
          which is not even at the level of a man page. The link in the first line of that document
          takes you to the same page. That is, it is a link to itself.

          That the documentation doesn't give examples of the interaction with Openbenchmarking.org
          is pathetic. Just look at the names that show up in the results in Openbenchmarking.org
          and you can see that people don't know what they are doing.

          Interestingly, by Googling, I found a link to more documentation: http://www.phoronix-test-suite.com/d...0/install.html
          but that link appears to be orphaned.

          I can't speak to if enterprise users have access to the documentation and
          the general public must get their documentation through the forums and by guessing.
          That's a marketing decision the developer must make.

          I would gladly help with the documentation, but I don't know how the software works.
          That's the point of my post.

          Comment


          • #6
            http://www.phoronix-test-suite.com/d...test-suite.pdf contains a lot, there's also a man page and HTML documentation that ships with the client, etc.
            Michael Larabel
            http://www.michaellarabel.com/

            Comment


            • #7
              Originally posted by deanjo View Post
              Code:
              1)        |   Big title showdown  |
              
                        /                        \
              2)   AMD                          Intel
                     |                               |
                     V                               V
              
              3)  Underclocked               Overclocked
               Running of Battery            Running on flux capacitor
              Get the idea now? In order for both results to be put together in a comparison, 1) must be the same on both runs for them to merge.
              Have to admit that this is the hardest part for me to understand even after reading the documentation. I completely get 1 and 2...but 3 still throws me off. Initially I thought it was a description for that particular leg of the benchmark but if I merge multiple into "Big title showdown" it only seems to appear once.

              So once I finally have multiple tests merged, I manually edit composite.xml in the test result to be a description encompassing all of the tests. Then I run "refresh-graphs" to get the description in there.

              Does it sound like I'm understanding / using it correctly?

              Comment

              Working...
              X