You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Pavel Afremov (JIRA)" <ji...@apache.org> on 2007/04/13 16:41:15 UTC

[jira] Created: (HARMONY-3651) [drlvm][jit][win-x64] Very slow compilation in Jitrino on Windows x86-64.

[drlvm][jit][win-x64] Very slow compilation in Jitrino on Windows x86-64.
-------------------------------------------------------------------------

                 Key: HARMONY-3651
                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
             Project: Harmony
          Issue Type: Bug
          Components: DRLVM
            Reporter: Pavel Afremov
            Priority: Minor
         Attachments: log.txt

Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.

Command:
~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest

Output:
.........................................
.........................................
.........
Time: 24.297

OK (91 tests)


real    2m35.573s
user    0m0.000s
sys     0m0.000s


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (HARMONY-3651) [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.

Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Varlamov reassigned HARMONY-3651:
----------------------------------------

    Assignee: Alexey Varlamov

> [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.
> ----------------------------------------------------------------
>
>                 Key: HARMONY-3651
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: winx64
>            Reporter: Pavel Afremov
>         Assigned To: Alexey Varlamov
>            Priority: Minor
>         Attachments: build.diff, log.txt
>
>
> Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.
> Command:
> ~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest
> Output:
> .........................................
> .........................................
> .........
> Time: 24.297
> OK (91 tests)
> real    2m35.573s
> user    0m0.000s
> sys     0m0.000s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-3651) [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.

Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Fursov updated HARMONY-3651:
------------------------------------

    Attachment: build.diff

build.diff:
Removing of STL checks for Jitrino in debug build for MSVC2005 gives 3x compilation time improvement.

> [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.
> ----------------------------------------------------------------
>
>                 Key: HARMONY-3651
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: winx64
>            Reporter: Pavel Afremov
>            Priority: Minor
>         Attachments: build.diff, log.txt
>
>
> Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.
> Command:
> ~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest
> Output:
> .........................................
> .........................................
> .........
> Time: 24.297
> OK (91 tests)
> real    2m35.573s
> user    0m0.000s
> sys     0m0.000s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-3651) [drlvm][winx64][jit] Very slow compilation in Jitrino on Windows x86-64.

Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky updated HARMONY-3651:
---------------------------------------

    Environment: winx64

> [drlvm][winx64][jit] Very slow compilation in Jitrino on Windows x86-64.
> ------------------------------------------------------------------------
>
>                 Key: HARMONY-3651
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: winx64
>            Reporter: Pavel Afremov
>            Priority: Minor
>         Attachments: log.txt
>
>
> Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.
> Command:
> ~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest
> Output:
> .........................................
> .........................................
> .........
> Time: 24.297
> OK (91 tests)
> real    2m35.573s
> user    0m0.000s
> sys     0m0.000s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (HARMONY-3651) [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.

Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Varlamov resolved HARMONY-3651.
--------------------------------------

    Resolution: Fixed

Fix applied at r541562. Please verify this speedup is enough.

> [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.
> ----------------------------------------------------------------
>
>                 Key: HARMONY-3651
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: winx64
>            Reporter: Pavel Afremov
>         Assigned To: Alexey Varlamov
>            Priority: Minor
>         Attachments: build.diff, log.txt
>
>
> Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.
> Command:
> ~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest
> Output:
> .........................................
> .........................................
> .........
> Time: 24.297
> OK (91 tests)
> real    2m35.573s
> user    0m0.000s
> sys     0m0.000s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-3651) [drlvm][winx64][jit] Very slow compilation in Jitrino on Windows x86-64.

Posted by "Pavel Afremov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Afremov updated HARMONY-3651:
-----------------------------------

    Summary: [drlvm][winx64][jit] Very slow compilation in Jitrino on Windows x86-64.  (was: [drlvm][jit][win-x64] Very slow compilation in Jitrino on Windows x86-64.)

> [drlvm][winx64][jit] Very slow compilation in Jitrino on Windows x86-64.
> ------------------------------------------------------------------------
>
>                 Key: HARMONY-3651
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Pavel Afremov
>            Priority: Minor
>         Attachments: log.txt
>
>
> Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.
> Command:
> ~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest
> Output:
> .........................................
> .........................................
> .........
> Time: 24.297
> OK (91 tests)
> real    2m35.573s
> user    0m0.000s
> sys     0m0.000s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HARMONY-3651) [drlvm][winx64][jit] Very slow compilation in Jitrino on Windows x86-64.

Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490919 ] 

Mikhail Fursov commented on HARMONY-3651:
-----------------------------------------

I check HWA application in debug mode on 32-bit and 64-bit Windows. Both PC has almost equal CPUs. Here are the results


Windows-IA32:
---Dump of counters begins---
action api_magic time=0.0125114
action bbp time=0.136583
action bp_regalloc time=0.449088
action btr time=0.159058
action cafl time=0.0947884
action cg_dce time=0.0996669
action constraints time=0.467618
action copy time=0.247639
action dce time=0.299596
action dessa time=0.00870796
action devirt time=0.053189
action early_prop time=0.0403096
action emitter time=0.425502
action gcmap time=0.422498
action gcpoints time=0.45046
action hir2lir time=0.721717
action i586 time=0.00247617
action i8l time=0.0711573
action info time=0.0302529
action inline time=1.23044
action layout time=0.185424
action lazyexc time=0.0311971
action lock_method time=0.00438911
action lower time=0.0700677
action markglobals time=0.0498712
action memopt time=3.51337
action native time=0.0118244
action opt_init time=0.00520827
action peephole time=0.1914
action purge time=0.00885843
action rce time=0.144565
action si_insts time=0.0205583
action simplify time=0.188796
action spillgen time=0.790963
action ssa time=0.104264
action stack time=0.104387
action statprof time=0.166369
action translator time=1.86793
action uce time=0.472344
action unlock_method time=0.00033566
ia32::gcmap::rt_enumerate=0
ia32::gcpoints::saveResults=0.0117872
ia32::gcpointsinfo::phase0=0.00562487
ia32::gcpointsinfo::phase1=0.471809
ia32::gcpointsinfo::phase1Checker=0.00764877
ia32::gcpointsinfo::phase2=0.0668208
ia32::gcpointsinfo::phase2Checker=0.046874
ia32::liveness=0.748777
ia32::packOpnds=0.035052
ia32::regAllocCheck=0.278713
ia32::selector::blockMerging=0.0378712
ia32::selector::fixNodeInfo=0.0764361
ia32::selector::selection=0.498016
ia32::spillgen:pass0=0.202455
ia32::spillgen:pass1=0.107542
ia32:regalloc2:assigned=11869
ia32:regalloc2:spilled=1624
ia32:regalloc3:assigned=0
ia32:regalloc3:coalesced=0
ia32:regalloc3:spilled=0
ia32:spillgen:emits=2025
ia32:spillgen:evicts=48
ia32:spillgen:preffered=21
ia32:spillgen:repairs=1
ia32:webmaker:splitted=0
opt::dce::phase1=0.0577802
opt::dce::phase2=0.0546299
opt::dce::phase3=0.0259605
opt::dce::phase4=0.0010319
opt::dce::phase5=0.0109749
opt::dce::phase6=0.0926561
opt::helper::computeDominators=0.329787
opt::helper::computeLoops=0.29976
opt::helper::fixupSsa=0.459452
opt::mem::phase1=2.79633
opt::mem::phase1b=0.0190713
opt::mem::phase1c=0.456666
opt::mem::phase1d=2.31826
opt::mem::phase2=0
opt::mem::phase3=0
ptra::fg::cleanupPhase=0.400034
ptra::fg::cleanupPhase::in=0.0119014
ptra::fg::inlineJSRs=0.115365
ptra::fg::inlineJSRs::defuse=0.0911942
total-compilation time=13.603
---Dump of counters ends---


Windows-EM64T:
---Dump of counters begins---
action bbp time=0.887884
action bp_regalloc time=10.5081
action cafl time=0.40527
action cg_dce time=0.928486
action constraints time=2.44831
action copy time=1.27316
action dce time=1.91098
action dessa time=0.0280308
action devirt time=0.264134
action emitter time=0.983473
action gcmap time=2.79911
action gcpoints time=2.60578
action hir2lir time=2.5076
action info time=0.31127
action inline time=4.25972
action layout time=2.70564
action lock_method time=0.0844732
action lower time=0.391598
action markglobals time=0.266119
action memopt time=36.3569
action native time=0.0339644
action opt_init time=0.00780164
action purge time=0.100806
action si_insts time=0.102582
action simplify time=0.777565
action spillgen time=2.9959
action ssa time=0.587405
action stack time=0.401629
action statprof time=1.22112
action translator time=4.31657
action uce time=2.97308
action unlock_method time=0.000386807
ia32::gcmap::rt_enumerate=0
ia32::gcpoints::saveResults=0.061352
ia32::gcpointsinfo::phase0=0.0197047
ia32::gcpointsinfo::phase1=3.58865
ia32::gcpointsinfo::phase1Checker=0.0346198
ia32::gcpointsinfo::phase2=0.164132
ia32::gcpointsinfo::phase2Checker=0.099675
ia32::liveness=2.73799
ia32::packOpnds=0.215967
ia32::regAllocCheck=0.621991
ia32::selector::blockMerging=0.338836
ia32::selector::fixNodeInfo=0.349665
ia32::selector::selection=1.54224
ia32::spillgen:pass0=0.741223
ia32::spillgen:pass1=0.455302
ia32:regalloc2:assigned=37057
ia32:regalloc2:spilled=1432
ia32:regalloc3:assigned=0
ia32:regalloc3:coalesced=0
ia32:regalloc3:spilled=0
ia32:spillgen:emits=2131
ia32:spillgen:evicts=13
ia32:spillgen:preffered=35
ia32:spillgen:repairs=3
ia32:webmaker:splitted=0
opt::dce::phase1=0.330294
opt::dce::phase2=0.195406
opt::dce::phase3=0.229258
opt::dce::phase4=0.00145824
opt::dce::phase5=0.10224
opt::dce::phase6=0.755745
opt::helper::computeDominators=1.84393
opt::helper::computeLoops=1.92217
opt::helper::fixupSsa=3.00243
opt::mem::phase1=33.165
opt::mem::phase1b=0.0985368
opt::mem::phase1c=4.27567
opt::mem::phase1d=28.8479
opt::mem::phase2=0
opt::mem::phase3=0
ptra::fg::cleanupPhase=2.2687
ptra::fg::cleanupPhase::in=0.0400985
ptra::fg::inlineJSRs=0.568377
ptra::fg::inlineJSRs::defuse=0.522087
total-compilation time=84.217


We do really have 6 times compilation time increase on Win64 platform.
One of the possible reasons can be more aggressive runtime checks in STL when compiled with MSVC2005.


> [drlvm][winx64][jit] Very slow compilation in Jitrino on Windows x86-64.
> ------------------------------------------------------------------------
>
>                 Key: HARMONY-3651
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Pavel Afremov
>            Priority: Minor
>         Attachments: log.txt
>
>
> Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.
> Command:
> ~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest
> Output:
> .........................................
> .........................................
> .........
> Time: 24.297
> OK (91 tests)
> real    2m35.573s
> user    0m0.000s
> sys     0m0.000s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-3651) [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.

Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky updated HARMONY-3651:
---------------------------------------

    Summary: [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.  (was: [drlvm][winx64][jit] Very slow compilation in Jitrino on Windows x86-64.)

> [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.
> ----------------------------------------------------------------
>
>                 Key: HARMONY-3651
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: winx64
>            Reporter: Pavel Afremov
>            Priority: Minor
>         Attachments: log.txt
>
>
> Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.
> Command:
> ~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest
> Output:
> .........................................
> .........................................
> .........
> Time: 24.297
> OK (91 tests)
> real    2m35.573s
> user    0m0.000s
> sys     0m0.000s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (HARMONY-3651) [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.

Posted by "Pavel Afremov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Afremov closed HARMONY-3651.
----------------------------------


Verified. Speed up is OK.

> [drlvm][jit] Very slow compilation in Jitrino on Windows x86-64.
> ----------------------------------------------------------------
>
>                 Key: HARMONY-3651
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: winx64
>            Reporter: Pavel Afremov
>            Assignee: Alexey Varlamov
>            Priority: Minor
>         Attachments: build.diff, log.txt
>
>
> Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.
> Command:
> ~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest
> Output:
> .........................................
> .........................................
> .........
> Time: 24.297
> OK (91 tests)
> real    2m35.573s
> user    0m0.000s
> sys     0m0.000s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-3651) [drlvm][jit][win-x64] Very slow compilation in Jitrino on Windows x86-64.

Posted by "Pavel Afremov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Afremov updated HARMONY-3651:
-----------------------------------

    Attachment: log.txt

Attached log.txt contains output with -verbose:em flag

> [drlvm][jit][win-x64] Very slow compilation in Jitrino on Windows x86-64.
> -------------------------------------------------------------------------
>
>                 Key: HARMONY-3651
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Pavel Afremov
>            Priority: Minor
>         Attachments: log.txt
>
>
> Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.
> Command:
> ~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest
> Output:
> .........................................
> .........................................
> .........
> Time: 24.297
> OK (91 tests)
> real    2m35.573s
> user    0m0.000s
> sys     0m0.000s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HARMONY-3651) [drlvm][jit][win-x64] Very slow compilation in Jitrino on Windows x86-64.

Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488699 ] 

Mikhail Fursov commented on HARMONY-3651:
-----------------------------------------

It's normal situation: JET is 10 times faster then OPT

Other  reasons of slow compilation time
1) Debug build turns a lot of additional and complex checking routines in OPT on.
2) Aggresive inlining parametes can make OPT compile more methods then JET

What are the timings for release builds?


> [drlvm][jit][win-x64] Very slow compilation in Jitrino on Windows x86-64.
> -------------------------------------------------------------------------
>
>                 Key: HARMONY-3651
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3651
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Pavel Afremov
>            Priority: Minor
>         Attachments: log.txt
>
>
> Kernel test "java.lang.ThreadTest" on JET works 15 seconds, but 2.5 minutes on OPT.
> Command:
> ~/trunk-debug-20070405/working_vm/build $ time deploy/jdk/jre/bin/java -Xbootclasspath/a:"../../working_classlib/depends/jars/junit_3.8.2/junit.jar;win_em64t_msvc_debug/semis/kernel.tests/classes" -Dtest.resource.path=win_em64t_msvc_debug/semis/kernel.tests/resources -Xem:opt junit.textui.TestRunner java.lang.ThreadTest
> Output:
> .........................................
> .........................................
> .........
> Time: 24.297
> OK (91 tests)
> real    2m35.573s
> user    0m0.000s
> sys     0m0.000s

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.