oracle systems _ nathan kroenert _ new software new hardware.pdf

The most comprehensive Oracle applications & technology content under one roof The most comprehensive Oracle applications & technology content under one roof

Replacing your So0ware? Time to consider your hardware.

Nathan Kroenert Frontline Systems Australia

and Melbourne Solaris Users Group ‘President’

The most comprehensive Oracle applications & technology content under one roof

Agenda

•  The evolu@on of SoBware •  The progression of hardware •  The ‘Exclusive Convergence’ of systems •  Improvements in interconnects •  Changes in APIs and interchange methodologies


Who am I? •  Nathan Kroenert •  Frontline Systems Na@onal Service Delivery Manager

•  Melbourne Solaris and Oracle Systems Users Group President

•  8 Years @ Sun: Educa@on, Tier 4 support, PreSales

•  4 years @ ANZ •  Considerable @me spent on Performance.


The Evolu@on of SoBware

•  The @mes the are a changin (Thanks, Bob) •  Much less about what the vendor gives you •  Much more about what the business wants the applica@on to do, with a range of op@ons

•  Influenced by open development •  Influenced by compe@@on •  Modularity is prolifera@ng


The Evolu@on of SoBware

•  Many systems being replaced are from the monolithic era.

•  New systems are typically much more externally dependent rather then request / result

•  Custom Binaries in C have moved more and more to layered architectures, J2EE, Web+App+DB, message busses and more

•  Ruby, Python, JAVA, C# -‐ all have considerable system level impact


Assump@ons of New SoBware

•  New SoBware oBen makes New System assump@ons

•  Much of the new soBware out there expects – Huge amounts of memory – Many threads – Very low latency interconnects – CPUs with hardware support for many func@ons


Solu@on when SoBware and Hardware are not a good match?


The Progression of Hardware

•  CPU’s no longer gedng drama@cally faster in a straight line – but are gedng WIDER

•  CPUs gedng more capability in silicone •  Memory System bandwidth increasing – though latency is not improving

•  Memory density increasing, but also not progressing nearly as fast as applica@ons can use it


The Progression of Hardware

•  Interconnects have improved •  Busses and loops have given way to fabrics (SAS, PCI-‐E, Infiniband)

•  ‘Commodity’ is a commodity term. •  Focus is oBen on CapEx – though oBen at the expense of OpEx.


Interconnects


Interconnects and caching

•  10Gbe Now, 40 and 100GbE coming soon •  QDR Infiniband here now (40Gbps), EDR and FDR already releasing

•  FLASH (Ah aaaaaah) •  SoBware gedng much smarter about using @ers WITHOUT external assistance (eg: 11gR2 using flash directly)


Hypervisors are cool, right?

•  To V or not to V! •  Why do we Virtualize? •  Regularly required because ‘the hardware is too big’, and because commodity hardware lacks many of the safeguards of Enterprise

•  The an@thesis of what makes sense in ‘large systems’. S@ll has value (eg: Availability)

•  Many and varied: Which should you use? When should you use them?


Clawing back the Datacentre

•  Racks of old systems can be consolidated into RU’s of space

•  Do in 200W what previously took 2000W •  Legacy support costs can be crippling •  Message passing speed of older plamorms (using PCI, PCI-‐X) are slower. Today is all about message speed

•  Increased reliability: ECC, Checksums, etc.


Exclusive Convergence vs Solu@ons

•  Many vendors have their own ‘convergence’ •  Most are claimed to be designed with a ‘system’ approach in mind, and are pitched as a ‘architected solu@on’

•  Many solu@ons are incompa@ble and force you into that vendors idea how it should be done.

•  The Oracle value is that you can use best of breed components, OR allow Oracle to provide the en@re stack.


COST

•  New hardware delivers more bang for buck •  Oracle Core Factor -‐ .25 for T3, .5 for M-‐series and X86, 1 for P-‐series, and Itanium largely irrelevant! ;)


Lifecycle WIN vs Expenditure FAIL

•  Infrastructure is typically only a small component of an IT project.

•  It’s typically the one chance for a to change it’s deployment architecture and to get onto the latest and greatest hardware

•  Provides the opportunity to build the right sized infrastructure rather than guessing

•  CPU capabili@es will be tracking soBware developments. Eg: DB specific instruc@ons


It’s great news: Your applica@on can be fast.


Get the MOST from your SoBware

•  Understanding your soBware helps architect a system to suit it

•  Select the right CPU architecture type •  Select the right memory architecture •  Balance I/O •  Use teiring intelligently, not just because you can

•  Agility in deployment: Virtual versus Physical


Summary:

•  Running new soBware on previous genera@on hardware is fraught with danger

•  Many soBware assump@ons don’t stack up on old hardware

•  Many applica@ons actually require instruc@on set support to run at their best

•  To get the most from your soBware applica@ons, the best start you can give them is a fresh batch of @n.


Ques@ons?

oracle systems _ nathan kroenert _ new software new hardware.pdf

Technology

oracle value

new systems

hardware support

buck oracle core factor

cost new hardware

greatest hardware

progression of hardware

ons inuenced