You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2007/05/18 11:14:16 UTC
[jira] Created: (HARMONY-3907) [drlvm][gc_gen] noticeable perf
degradation on drlvm tests
[drlvm][gc_gen] noticeable perf degradation on drlvm tests
----------------------------------------------------------
Key: HARMONY-3907
URL: https://issues.apache.org/jira/browse/HARMONY-3907
Project: Harmony
Issue Type: Bug
Components: DRLVM
Reporter: Alexey Varlamov
This is a placeholder for tracking general problem:
I checked my perceived changes in pre-commit testing time after
Harmony switched to gcv5, comparing with old gc_cc on the following
test:
> sh build.sh -DBUILD_CFG=<cfg> -Dtest.mode=jet test -Dtest.vmargs="-XX:vm.dlls=<gc>"
Some smoke tests (outofmemory.*, perf.SeveralThreads, etc)
intermittently fail/hang on gc_gen, so I've run each configuration 2-3
times. All machines are multicore (>= 2 CPUs) server boxes.
Ant-reported build time records are listed below:
avg time in sec, gc_cc / gc_gen
--------------------------------------------
Win32 release: 340 / 520
Win32 debug: 620 / 1400
Linux32 release: 300 / 1200
Linux32 debug: 440 / 1000
Linux64 debug: 550 / 1300
Indeed the time for testing is increased at least twice with gc_gen!
The gc_gen timing is probably somewhat better since HARMONY-3875 commit, but still noticeably worse.
The perceived degradation is most evident in stressing smoke tests like perf.* and outofmemory.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-3907) [drlvm][gc_gen] noticeable perf
degradation on drlvm tests
Posted by "Xiao-Feng Li (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496819 ]
Xiao-Feng Li commented on HARMONY-3907:
---------------------------------------
Hi, Alexey, I don't think this is a bug. And I don't understand why you think this issue needs major priority.
> [drlvm][gc_gen] noticeable perf degradation on drlvm tests
> ----------------------------------------------------------
>
> Key: HARMONY-3907
> URL: https://issues.apache.org/jira/browse/HARMONY-3907
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Alexey Varlamov
>
> This is a placeholder for tracking general problem:
> I checked my perceived changes in pre-commit testing time after
> Harmony switched to gcv5, comparing with old gc_cc on the following
> test:
> > sh build.sh -DBUILD_CFG=<cfg> -Dtest.mode=jet test -Dtest.vmargs="-XX:vm.dlls=<gc>"
> Some smoke tests (outofmemory.*, perf.SeveralThreads, etc)
> intermittently fail/hang on gc_gen, so I've run each configuration 2-3
> times. All machines are multicore (>= 2 CPUs) server boxes.
> Ant-reported build time records are listed below:
> avg time in sec, gc_cc / gc_gen
> --------------------------------------------
> Win32 release: 340 / 520
> Win32 debug: 620 / 1400
> Linux32 release: 300 / 1200
> Linux32 debug: 440 / 1000
> Linux64 debug: 550 / 1300
> Indeed the time for testing is increased at least twice with gc_gen!
> The gc_gen timing is probably somewhat better since HARMONY-3875 commit, but still noticeably worse.
> The perceived degradation is most evident in stressing smoke tests like perf.* and outofmemory.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-3907) [drlvm][gc_gen] noticeable perf
degradation on drlvm tests
Posted by "Pavel Afremov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497378 ]
Pavel Afremov commented on HARMONY-3907:
----------------------------------------
On my Pentium M laptop under Windows XP for x86-32 I have following results:
gc v 4.1 / gc v 5
gc.SynchronizedFinalizersTest 0m3.524s / 6m18.514s Fix proposed in HARMONY-3668.
100 * gc.Finalizer 1m31.408s / 2m29.110s
100 * gc.FinAlloc 3m15.562s / 4m31.658s
10 * gc.Force 0m8.403s / 0m12.919s
10 * gc.Free 0m8.313s / 0m14.083s
10 * gc.List 0m10.827s / 0m15.995s
gc.Mark 0m6.937s / 0m10.087s
10 * gc.PhantomReferenceQueueTest 0m9.460s / 0m13.240s
10 * classloader.StressLoader 0m23.841s / 0m28.341s
> [drlvm][gc_gen] noticeable perf degradation on drlvm tests
> ----------------------------------------------------------
>
> Key: HARMONY-3907
> URL: https://issues.apache.org/jira/browse/HARMONY-3907
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Alexey Varlamov
> Assigned To: Xiao-Feng Li
>
> This is a placeholder for tracking general problem:
> I checked my perceived changes in pre-commit testing time after
> Harmony switched to gcv5, comparing with old gc_cc on the following
> test:
> > sh build.sh -DBUILD_CFG=<cfg> -Dtest.mode=jet test -Dtest.vmargs="-XX:vm.dlls=<gc>"
> Some smoke tests (outofmemory.*, perf.SeveralThreads, etc)
> intermittently fail/hang on gc_gen, so I've run each configuration 2-3
> times. All machines are multicore (>= 2 CPUs) server boxes.
> Ant-reported build time records are listed below:
> avg time in sec, gc_cc / gc_gen
> --------------------------------------------
> Win32 release: 340 / 520
> Win32 debug: 620 / 1400
> Linux32 release: 300 / 1200
> Linux32 debug: 440 / 1000
> Linux64 debug: 550 / 1300
> Indeed the time for testing is increased at least twice with gc_gen!
> The gc_gen timing is probably somewhat better since HARMONY-3875 commit, but still noticeably worse.
> The perceived degradation is most evident in stressing smoke tests like perf.* and outofmemory.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-3907) [drlvm][gc_gen] noticeable perf
degradation on drlvm tests
Posted by "Xiao-Feng Li (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao-Feng Li reassigned HARMONY-3907:
-------------------------------------
Assignee: Xiao-Feng Li
> [drlvm][gc_gen] noticeable perf degradation on drlvm tests
> ----------------------------------------------------------
>
> Key: HARMONY-3907
> URL: https://issues.apache.org/jira/browse/HARMONY-3907
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Alexey Varlamov
> Assigned To: Xiao-Feng Li
>
> This is a placeholder for tracking general problem:
> I checked my perceived changes in pre-commit testing time after
> Harmony switched to gcv5, comparing with old gc_cc on the following
> test:
> > sh build.sh -DBUILD_CFG=<cfg> -Dtest.mode=jet test -Dtest.vmargs="-XX:vm.dlls=<gc>"
> Some smoke tests (outofmemory.*, perf.SeveralThreads, etc)
> intermittently fail/hang on gc_gen, so I've run each configuration 2-3
> times. All machines are multicore (>= 2 CPUs) server boxes.
> Ant-reported build time records are listed below:
> avg time in sec, gc_cc / gc_gen
> --------------------------------------------
> Win32 release: 340 / 520
> Win32 debug: 620 / 1400
> Linux32 release: 300 / 1200
> Linux32 debug: 440 / 1000
> Linux64 debug: 550 / 1300
> Indeed the time for testing is increased at least twice with gc_gen!
> The gc_gen timing is probably somewhat better since HARMONY-3875 commit, but still noticeably worse.
> The perceived degradation is most evident in stressing smoke tests like perf.* and outofmemory.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (HARMONY-3907) [drlvm][gc_gen] noticeable perf
degradation on drlvm tests
Posted by "Xiao-Feng Li (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao-Feng Li closed HARMONY-3907.
---------------------------------
Resolution: Won't Fix
It's not an issue.
> [drlvm][gc_gen] noticeable perf degradation on drlvm tests
> ----------------------------------------------------------
>
> Key: HARMONY-3907
> URL: https://issues.apache.org/jira/browse/HARMONY-3907
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Alexey Varlamov
> Assignee: Xiao-Feng Li
>
> This is a placeholder for tracking general problem:
> I checked my perceived changes in pre-commit testing time after
> Harmony switched to gcv5, comparing with old gc_cc on the following
> test:
> > sh build.sh -DBUILD_CFG=<cfg> -Dtest.mode=jet test -Dtest.vmargs="-XX:vm.dlls=<gc>"
> Some smoke tests (outofmemory.*, perf.SeveralThreads, etc)
> intermittently fail/hang on gc_gen, so I've run each configuration 2-3
> times. All machines are multicore (>= 2 CPUs) server boxes.
> Ant-reported build time records are listed below:
> avg time in sec, gc_cc / gc_gen
> --------------------------------------------
> Win32 release: 340 / 520
> Win32 debug: 620 / 1400
> Linux32 release: 300 / 1200
> Linux32 debug: 440 / 1000
> Linux64 debug: 550 / 1300
> Indeed the time for testing is increased at least twice with gc_gen!
> The gc_gen timing is probably somewhat better since HARMONY-3875 commit, but still noticeably worse.
> The perceived degradation is most evident in stressing smoke tests like perf.* and outofmemory.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-3907) [drlvm][gc_gen] noticeable perf
degradation on drlvm tests
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496837 ]
Alexey Varlamov commented on HARMONY-3907:
------------------------------------------
Xiao-Feng, which category would you suggest then?
As for the priority, this issue really affects most people developing DRLVM, and I suspect it may affect Harmony users' experience in unwanted way. If we keep gc_gen the default GC, it should be outstanding one among neighbour impls in all important aspects, do you agree? And performance is very important aspect for GC.
> [drlvm][gc_gen] noticeable perf degradation on drlvm tests
> ----------------------------------------------------------
>
> Key: HARMONY-3907
> URL: https://issues.apache.org/jira/browse/HARMONY-3907
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Alexey Varlamov
> Assigned To: Xiao-Feng Li
>
> This is a placeholder for tracking general problem:
> I checked my perceived changes in pre-commit testing time after
> Harmony switched to gcv5, comparing with old gc_cc on the following
> test:
> > sh build.sh -DBUILD_CFG=<cfg> -Dtest.mode=jet test -Dtest.vmargs="-XX:vm.dlls=<gc>"
> Some smoke tests (outofmemory.*, perf.SeveralThreads, etc)
> intermittently fail/hang on gc_gen, so I've run each configuration 2-3
> times. All machines are multicore (>= 2 CPUs) server boxes.
> Ant-reported build time records are listed below:
> avg time in sec, gc_cc / gc_gen
> --------------------------------------------
> Win32 release: 340 / 520
> Win32 debug: 620 / 1400
> Linux32 release: 300 / 1200
> Linux32 debug: 440 / 1000
> Linux64 debug: 550 / 1300
> Indeed the time for testing is increased at least twice with gc_gen!
> The gc_gen timing is probably somewhat better since HARMONY-3875 commit, but still noticeably worse.
> The perceived degradation is most evident in stressing smoke tests like perf.* and outofmemory.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.