Quite right. You have to consider the whole stack, from storage/networking to
the hipervisor, guest OS, database and the applications.
If you only consider that a Xeon is cheaper than an IFL it is anybody's guess
what the final functional outcome for the customer will be.
Just to add 5 cents.
Besides hardware, you also changed database which may have HUGE impact on
performance.
03-02-2016 01:28:09 "Harder, Pieter" wrote:
>In fact the disk system didn't change with our migration. The VMWare farm
was
>run against the same IBM DS8000 the z used. Most of the DS8000
Don't forget to add the required resources with management and maintenance
for DR, dev/test/Q (after all, who runs production only workloads?).
- And then add z Systems push pull process into the refresh mix...
Something that is often overlooked by competitive comparisons.
Kurt Acker
Cell:
I apologize for bad typing
There is no good TCO tool for this, the IBM tools come close. It's not just
about the io, the chip speed, the ability to push pull,to offload io onto other
chips. It's about all things. No x86 platform has the scads of shared cache at
multiple levels of the
And power, cooling, floorspace, etc.
Lee Stewart ● VM System Support ● Visa ● Phone: 6(750)4601 - +1-303-389-4601 ●
lstew...@visa.com
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Harder, Pieter
> Sent: Wednesday, February 03, 2016 3:39
I believe that the x86 platform we would be moving to would be a Linux
implementation running under vmware using IIB/MQ, WAS, and DB2. I not sure if
the memory requirements for a database server would apply when running under
Linux. We have a rather larger database accessed by a zLinux DB2
