All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Evanchik <evanchsa@clarkson.edu>
To: Manfred.Herrmann@zipptec.de
Cc: xen-devel@lists.sourceforge.net
Subject: Re: questions about production use
Date: 23 Jan 2004 20:09:40 -0500	[thread overview]
Message-ID: <1074906579.23885.37.camel@localhost> (raw)
In-Reply-To: <OFAF7FE5E4.3D118134-ONC1256E24.0052CE18-C1256E24.005FEE5C@zipptec.de>

On Fri, 2004-01-23 at 12:26, Manfred.Herrmann@zipptec.de wrote:

> The following technologies/architectures are on my research list and
> my
> stupid thoughts about the differences.
> 
> xen -> pros:
>    - near to "mainframe" architecture

<snip>

> IBM mainframe Linux ... mainframe to expensive for me :-)

Comparing Xen to an IBM zSeries mainframe is not really fair. The IBM
boxes are much more than just virtualization and resource partitioning
there's a whole support structure around these things. There's a reason
they boast 5 9's of reliability -- because it actually happens. Try that
with a single Intel machine and you'll find that it's fairly difficult
if not impossible. It's not always that easy though. 

With that said, if you directly compare a zSeries mainframe to a dual
Xeon you'll find that the dual Xeon is much more capable of handling the
workloads you are most familiar with. 

Kernel compilation times are measured in a few minutes on the Xen
guests, whereas our z800 takes on the order of 30 minutes. That's just
one example, the top end of a fully loaded z800 (or even z900/z990) is
far too expensive if you just compare performance expectations side by
side.

Our z800 can scale very well considering that it is only 1 machine.. but
for the cost of scaling it up you could have purchased a few hundred
Intel machines and done a much better job or more realistically a few
dozen to keep support costs lower.


All in all we've been very happy playing with Xen here. Our z800 is
nice, but I'm not sure that we are the right kind of people to use it
effectively. It always seems we push it outside of its designed
specification.

Stephen








-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  parent reply	other threads:[~2004-01-24  1:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040123145905.A9C0D1102@gg104015.zipptec.de>
2004-01-23 17:26 ` questions about production use Manfred.Herrmann
2004-01-23 17:37   ` Ian Pratt
2004-01-23 20:01     ` Nick Craig-Wood
2004-01-23 19:46   ` Nick Craig-Wood
2004-01-24  1:09   ` Stephen Evanchik [this message]
2004-01-23 20:26 Williamson, Mark A
2004-01-24  8:46 ` Nick Craig-Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1074906579.23885.37.camel@localhost \
    --to=evanchsa@clarkson.edu \
    --cc=Manfred.Herrmann@zipptec.de \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.