The proper response is: "It depends".
Depends a lot on how much memory you have on the machine, what jvm you
use, and how fast disks spin as well as processor capacity and
availability.
It will (almost) never keep up with a stand-alone x86 box running
Windows or *nix. There are exceptions where the application will run
better on i than Windows, particularly where the database to access is
on the i and the i has lots of processors.
The paging algorithms for single level store don't necessarily work well
with a java application with a big footprint. The gc keeps going out and
touching those pages that just swapped out. You'll see a lot of non-DB
page faults. If you can keep the whole heap in memory you avoid this
problem.
Objects take up a lot less heap space with the 32 bit versions of the
JVM.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Thursday, February 04, 2010 3:26 PM
To: Midrange Systems Technical Discussion
Subject: Java performance on the i ? Good? bad? OK?
Java performance on the i ? Good? Bad? OK?
I am being told that "Java on the i sucks." What is the proper
response?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.