Question about BurnInTest 3D Graphics Cycles accumulatio

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • cahozhang
    Member
    • Dec 2021
    • 84

    #1

    Question about BurnInTest 3D Graphics Cycles accumulatio

    Hello PassMark Support,

    I am checking a BurnInTest report and would like to confirm whether the 3D Graphics Cycles value is expected to accumulate into the overall total normally.

    In my test log, the 3D Graphics section shows the cycle count increasing in steps, for example:
    • 4
    • 8
    • 12
    • 16
    • 20

    So it looks like it is increasing by completed test loops rather than continuously.

    I would like to confirm:
    1. Is the 3D Graphics Cycles count included in the overall accumulated total for the test session?
    2. Is it normal for the 3D Graphics cycle count to increase in blocks rather than increase continuously like some other test items?
    3. What is the expected relationship between Cycles and Operations in the 3D Graphics test?
    4. If the log shows "No operations reported in timeout period", does that mean the 3D test stopped updating abnormally, or can this still be considered normal behavior under some conditions?

    From our observation, the count does increase, but the pattern is different from other test items, so we want to confirm whether this is expected behavior.

    Thank you.
    Attached Files
  • Richard (PassMark)
    Administrator
    • May 2010
    • 960

    #2
    1. Is the 3D Graphics Cycles count included in the overall accumulated total for the test session?
    2. Is it normal for the 3D Graphics cycle count to increase in blocks rather than increase continuously like some other test items?
    3. What is the expected relationship between Cycles and Operations in the 3D Graphics test?
    A single cycle of the 3D Test is every 30 seconds of the 3D actual runtime. Likely you have set 2 minutes as the Logging interval, therefore, in your "interim periodic report", cycle count would increase by 4 (120secs/30secs) each periodic report. The operations for the 3D test is the total number frames rendered.

    4. If the log shows "No operations reported in timeout period", does that mean the 3D test stopped updating abnormally, or can this still be considered normal behavior under some conditions?
    The No Operations reported in Timeout reported by the test means that the test didn't perform any operations for a test duration, the duration is currently set to 2 minutes. So, it is a warning that the test is not running for a period. This can be caused by the test 'locking' up or if the system is under heavy load, the driver crashed, or possibly the 3D application unexpectedly close. For the 3D Test, the test is performed in a separate executable. The test is set to close and to be restarted every 900 seconds or when the No operations warning occurs. This is to allow for the test to restart (e.g. driver crash).

    Comment

    • cahozhang
      Member
      • Dec 2021
      • 84

      #3
      When I run the burn-in 3D Graphic test ,I noticed that the Cycle count resets to 0 approximately every 15 minutes and then starts counting again, Is this a special setting in the software? As attached video . 2.Can I modify it to make the Cycle count accumulate continuously? How can I configure this?

      Comment

      • Simon (PassMark)
        Administrator
        • Apr 2021
        • 313

        #4
        We were able to reproduce the cycle count issue, will be fixed for the next build.

        Comment

        Working...