| 1 |
On Sun, 2007-05-27 at 15:02 +0100, robert burrell donkin wrote: |
| 2 |
> |
| 3 |
> > > So, this particular problem isn't occurring w/ sun-jdk-1.6.0 on amd64? |
| 4 |
> > |
| 5 |
> > Correct, all Sun jdks other than 1.5 are fine. Both 1.6.0.x and 1.7 |
| 6 |
> > which is openjdk are fine. |
| 7 |
> > |
| 8 |
> > > Maybe I'd be better off just upgrading to 6 rather than fighting w/ 5 on |
| 9 |
> > > 64bit. |
| 10 |
> > |
| 11 |
> > I would recommend doing so. |
| 12 |
> |
| 13 |
> +1 |
| 14 |
> |
| 15 |
> there are a number of other server apps which i can't run on that JVM on AMD64 |
| 16 |
|
| 17 |
Interesting. Further testing revealed that sun-jdk-1.5.0.11's behavior |
| 18 |
is consistent on all amd64 procs. Despite earlier statements about it |
| 19 |
not failing on Turions. Compiling Tomcat 6.0.x with 1.5.0.11 on amd64 |
| 20 |
fails always, less memory is increased or compiler is switched to ecj |
| 21 |
from javac. |
| 22 |
|
| 23 |
Beyond that 1.5 and 1.6 seem to have the same default allocations, |
| 24 |
except for initial starting min value. 1.5.0.11 stars with like 4mb, and |
| 25 |
1.6 starts with ~7mb. Their max is the same default. ~64mb on x86, and |
| 26 |
~84-96mb on amd64. |
| 27 |
|
| 28 |
But there still might be other things in the jvm that are undesirable |
| 29 |
performance and etc wise in 1.5.0.x. Which they address in 1.6 or etc. |
| 30 |
|
| 31 |
-- |
| 32 |
William L. Thomson Jr. |
| 33 |
Gentoo/Java |
Archives