[Xen-ia64-devel] Weekly benchmark results [ww28]

["yo.fujita" <yo.fujita@xxxxxxxxxxxxxxxx>]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
    Machine          : Tiger4
    KERN             : 2.6.16.13-xen
    changeset        : 10694:79a5833d1266
    Dom0 OS          : RHEL4 U2 (no SMP)
    DomU OS          : RHEL4 U2 (2P)
    No. of DomU's    : 1
    Sched            : credit

issues: 
     - As Alex said, we also saw too many Oops messages as below by some
benchmark
      tests.
       Oops: timer tick before it's due (itc=149ddec9a47,itm=149de296e2e)

     - And oom-killer occurred in domU as LMbench finished.
      (see attached oom-killer.log)

     - I think this time benchmark tests is very unstable,
       because the following problem occurred in domU frequently on
executing 
       many kinds of tests.
       1. No response suddenly when benchmark testing.
       2. Ping was OK, but SSH didn't work when the case 1 happened.
       3. DomU status in xm list was "b(=blocked)" when case 1 happened.


TEST RESULT
    unixbench4.1.0    : Pass (once in 3 times testing)
    bonnie++-1.03　   : Pass
    ltp-full-20060306 : 3/817 FAIL (see attachment)
    iozone3_191       : Pass (once in 2 times testing)
    lmbench-3.0-a5    : Pass (once in 2 times testing)
# The detail of failure was already shown.

Thanks and best regards,
Fujita and Fujitsu members

ltp-domU-20060713.log
Description: Binary data

oom-killer.log
Description: Binary data

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel