The old school that thinks 80 mips is a lot is used to
really well written programs, written in assembler to
be efficient in both CPU and storage.  The new school
that uses Java and C++ has different objectives.

An 80 MIP processor is about a 300MHz pentium. This is
based on "Barton's Number of 4", where 1 mip is about
4 Mhz of Intel running equivalent code.  Not a really
impressive machine, unless it is running many workloads
at a very high utilization with lots of I/O 7 x 24....

I've heard the new java compilers are much much better,
suited more for meeting mainframe objectives.


>From: David Booher <[EMAIL PROTECTED]>
>
>Brandon,
>
>I feel your pain.  We have a z800-0X2 and even when DEDICATEing
>an entire processor (roughly 80 MIPS) to a single VM guest
>(Linux or z/OS) running WebSphere we see TERRIBLE performance.
>It consumes the entire 80 MIPS for several minutes during
>WebSphere initialization and then the demo app, PetStore, runs
>very very slowly. Plant Store is not much better.
>
>I'm from the old school, and 80 MIPS is a LOT, I mean, A LOT of
>processor power to throw at an App Server.  WebSphere is no CICS,
>that's for sure!
>
>David Booher, Systems Programmer
>Quest  Software
>4320 Winfield Rd, Suite 500
>Warrenville, IL  60555
>630.836.3196
>http://www.quest.com
>
>
>-----Original Message-----
>From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
>Brandon Darbro
>Sent: Friday, June 18, 2004 1:11 PM
>To: [EMAIL PROTECTED]
>Subject: J2EE performance?
>
>
>I've had the opportunity to play with JBOSS recently, as well as
>watch some Websphere testing on our linux guests, and I'm not
>very happy with the performance and resource utilization.
>
>Let's see... what can I tell you about our system:
>
>* z800
>* 2 IFL's (tested using single and dual, still slow) in LPAR
>* z/VM 4.4.0
>* guest lan networking
>* 256 meg RAM
>* 512 meg vdisk swap
>
>Observations:
>
>* Turning of hz_timer patch helps lower CPU utilization footprint of
>the java processes, but of course, then the system never sleeps.
>* When running a J2EE app, it takes often over a minute to finish
>rendering a page to a browser.
>* When running a J2EE app, java consumes an entire IFL of cpu if we let
>it.
>
>I understand others are successfully running J2EE implimentations on
>mainframe Linux, so here are my questions:
>
>1.  Is J2EE a cpu resource hog for you?
>2.  Are you running Linux under VM or right on the LPAR?
>3.  Do you charge users for MIP usage?  If so, how does this high CPU
>utilization not eat your customer alive in billed costs?
>4.  Does anyone have some advice on how to run J2EE services more
>efficiently, faster and easier on cpu?
>5.  Which J2EE server software for mainframe Linux do you prefer and
>why?
>6.  Lastly, why would you choose to run J2EE on mainframe Linux as
>apposed to some stand-alone system (Unix, Windows, Other)?
>
>Thanks folks,
>*Brandon Darbro








"If you can't measure it, I'm Just NOT interested!"(tm)

/************************************************************/
Barton Robinson - CBW     Internet: [EMAIL PROTECTED]
Velocity Software, Inc    Mailing Address:
 196-D Castro Street       P.O. Box 390640
 Mountain View, CA 94041   Mountain View, CA 94039-0640

VM Performance Hotline:   650-964-8867
Fax: 650-964-9012         Web Page:  WWW.VELOCITY-SOFTWARE.COM
/************************************************************/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to