I tried using JDK-1.6.0 to profile a large application. Normally the app is up and running in about 3 minutes. With -Xprof, we had to kill it after about 35 minutes because it had only gotten through about half of the application initialization code.
I don't have good logs to show with and without -Xprof, but it should be easy to reproduce.
Preliminary testing on a 2xOpteron win32 systems suggests that the fix for 6415670 may provide relief. We'll ask for the bug to be reevaluated after that fix is made available.
I don't have good logs to show with and without -Xprof, but it should be easy to reproduce.
Preliminary testing on a 2xOpteron win32 systems suggests that the fix for 6415670 may provide relief. We'll ask for the bug to be reevaluated after that fix is made available.
- duplicates
-
JDK-6415670 On allocating memory for threads on a dual core results in no CPU
-
- Closed
-
- relates to
-
-
- Closed
-
-
JDK-4689885 Solaris reliability: stop using thr_suspend
-
- Closed
-