DOCSLIB.ORG

Optimizing Vmware Vsan™ Performance on a Dell EMC® Poweredge™ R7525 Server with Nvme™ Namespaces and KIOXIA CM6 Series Ssds

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Optimizing Vmware Vsan™ Performance on a Dell EMC® Poweredge™ R7525 Server with Nvme™ Namespaces and KIOXIA CM6 Series Ssds Reference Architecture Optimizing VMware vSAN™ Performance on a Dell EMC® PowerEdge™ R7525 Server with NVMe™ Namespaces and KIOXIA CM6 Series SSDs Published May 2021 KIOXIA: Tyler Nelson Adil Rahman Scott Harlin Participating Companies: AMD, Inc. Dell, Inc. VMware®, Inc. Table of Contents Introduction . .3 Background . 3 The Industry Challenge . 4 System Architecture . .4 System Configuration . .4 Hardware Configuration . 5 Host Installation / VMware vCenter Setup . 5 Network Configuration . 6 VMkernel Adapter Configuration . .7 NVMe Namespace Configuration . 8 Cluster Configuration . .9 VMware vSAN Configuration . 10 Creating Fault Domains . .11 Creating VM Storage Policies . .11 Test Methodology . .13 Test Cases . .13 Test Results . 13 Without NVMe Namespaces . .13 With Two (2) NVMe Namespaces . .14 With Five (5) NVMe Namespaces . .14 With Eight (8) NVMe Namespaces . .15 Summary of IOPS Performance . .15 Summary of Throughput Performance . .16 Test Analysis . .17 Recommendations . 18 Summary . .18 Summary of Tuning Parameters and Settings . 19 Reference Architecture Introduction This reference architecture (RA) presents the synergy between NVMe protocol namespaces and VMware vSAN virtualization software to demonstrate increases in SSD input/output operations per second (IOPS) performance. It includes hardware and software tuning, and the test process, methodology, results and analysis for a configuration that features a Dell EMC PowerEdge R7525 rack server with two-socket AMD EPYC™ CPUs and the ability to utilize up to twenty-four (24) PCIe® 4.0 NVMe SSDs per server. The testing conducted showcases the raw computing power of a hyper-converged infrastructure (HCI) in combination with fast, scalable local storage. Using an aggregate of twelve (12) KIOXIA CM6 Series PCIe 4.0 NVMe SSDs, the configuration was able to achieve random read performance up to 896,555 IOPS1. Configuration variability is also addressed to enable storage architects, system integrators, channel partners and other key stakeholders to create flexible designs that scale up to meet data center compute and storage needs. An optimal configuration is also presented that will help application administrators and storage architects obtain optimal storage performance from this configuration. Additional benefits include: Summary A Dell EMC PowerEdge R7525 server cluster with KIOXIA CM6 Series PCIe 4.0 NVMe SSDs demonstrates impressive IOPS and throughput performance, with low-latencies in a vSAN HCI environment More clusters and drives increase system performance as vSAN virtualization performance scales with the cluster size and available SSDs NVMe protocol namespaces with vSAN virtualization enables full utilization of CM6 Series SSD capacity: • Into both cache and capacity tiers • Paramount in scaling local storage when duplicated in HCIs Efficient scaling of compute and storage resources reduces data center cost without sacrificing quality vSAN virtualization with NVMe namespaces are applicable to many different real-world workloads Background Businesses rely on IT specialists to assemble the compute, storage and networking resources for their respective data centers and to address critical demands such as exponential data growth, technological advances and constant upgrades to hardware resources. Having to upgrade hardware for each resource pool is both expensive in cost and in lost productivity as the upgrades require additional testing to determine compatibility with the pre- existing infrastructure. These hardware challenges have pushed many IT departments to move to a software-defined, HCI approach that virtualizes compute and storage resources using a combination of commercially-available server hardware and very fast SSDs for local-attached storage. Each hyper-converged compute/ storage node in the virtualized cluster runs a hypervisor that contributes its resources into a cluster of other hyper-converged nodes. The hypervisors are controllable by management software to form and manage the server clusters, and to assign resource allocations depending on individual virtual machine (VM) needs. The HCI approach enables data centers to evolve with small server clusters and/or scaled storage based on their unique business requirements. For this RA, KIOXIA selected VMware Inc. components that included the VMware ESXi™ hypervisor, VMware vSphere® enterprise-scale virtualization platform, and VMware vCenter® management software, as they are helping to evolve HCIs. These platforms serve to abstract compute resources from various hosts into a cluster of resources that can be provisioned for use by VMs or containers. When VMware vSAN enterprise-class, storage virtualization software is combined with VMware vSphere, IT departments can manage compute and storage resources within a single platform. VMware vSAN software integrates seamlessly with the VMware vSphere stack for easy management, and the KIOXIA CM6 Series SSDs and namespace configuration helps to minimize latency and deliver fast IOPS performance. It also can utilize NVMe SSDs as local storage enabling them to be divided into cache and capacity tiers to increase performance. © 2021 KIOXIA Corporation. All rights reserved. Reference Architecture | Optimizing VMware vSAN™ Performance on a Dell EMC® PowerEdge™R7525 Server with NVMe™ Namespaces and KIOXIA CM6 Series SSDs | May 2021 | Rev. 1.0 https://business.kioxia.com/ 3 Reference Architecture NVMe SSDs are recommended for HCIs and represent the latest and fastest protocol for flash-based storage media. They are built on the high-speed PCIe interface that uses lanes to directly connect to the CPU and delivers significantly improved performance and low-latency versus SAS and SATA options. The NVMe protocol can support up to 65,535 input/output (I/O) queues, each having 65,535 commands per queue, where multiple CPU cores can access the queues in parallel simultaneously. The NVMe protocol also supports namespaces that enable individual logical block addresses (LBA) to be accessible to host software, and each LBA has a namespace ID that the underlying storage controller uses to identify it as a unique drive. Before the NVMe protocol existed, an SSD would need to be dedicated as a cache OR capacity drive as VMware vSAN software was only able to utilize 600 gigabyte2 (GB) of a cache drive. It is common for the cache drives to partially utilize capacity, which in turn negatively impacted the ability to scale local-based storage. Using namespaces, SSD capacity can be fully utilized as both cache AND data storage. The Industry Challenge In an HCI, entire disks are used for caching while others are used for data. There are also limits to the number of cache devices and disk groups that can be used. Each cache device in VMware software requires an entire disk be allocated to cache with a limited cache size of 600GB. To obtain optimal performance from a dedicated cache SSD, a system administrator would need to purchase one 3 DWPD3, 800GB or 1.6 terabyte2 (TB) SSD and allocate the entire disk to cache. This process is highly inefficient, under-utilizes the capacity of higher end and faster performing SSDs, and makes it difficult to scale storage capacities independent of nodes, forcing system admins to use lower performing SSDs to meet the cache requirements. System Architecture The system architecture and associated SSDs were selected, with different configurations tested, to determine an optimal setup. KIOXIA CM6 Series PCIe 4.0 NVMe SSDs with 7.68TB capacities were chosen for their PCIe 4.0 capability and DWPD. In order to utilize namespaces (so that the SSD can perform as both a cache and data storage), larger capacity points were selected to utilize higher overall data written per day. Instead of using a smaller 3 DWPD SSD for cache, a larger 1 DWPD drive was chosen so that the SSD can utilize higher overall data written per day as follows: 7.68TB x 1 DWPD = 7.68TB written per day VS 800GB x 3 DWPD = 2.4TB written per day The larger drive allows a higher overall daily data write than a smaller 3 DWPD SSD. Testing was then conducted to demonstrate the performance of the configuration running NVMe namespaces and VMware vSAN software. The system configuration used for testing included: System Configuration Server Configuration: Dell EMC PowerEdge R7525 Total number of systems 3 BIOS and version PowerEdge R7525 Version 1.7.3 Operating system and version VMWare ESXi 7.0.1 17325551 U1 P25 Last date of OS patching 10/05/2020 Power management policy High performance Processor Configuration: Number of processors 2 Vendor and model AMD EPYC 7552 48-Core Processor Core count 48 Core frequency 2200 MHz Stepping 0 Memory Module Configuration: Total system memory 256 GB Number of memory modules 16 Vendor and model Micron® MTA18ASF2G72PDZ-2G9E1TI 16 GB 2RX8 PC4-2933Y-RE2-12 © 2021 KIOXIA Corporation. All rights reserved. Reference Architecture | Optimizing VMware vSAN™ Performance on a Dell EMC® PowerEdge™R7525 Server with NVMe™ Namespaces and KIOXIA CM6 Series SSDs | May 2021 | Rev. 1.0 https://business.kioxia.com/ 4 Reference Architecture Size 16 GB Type ECC DDR-4 Speed (MHz) 2933 MHz NVMe SSD Configuration: Number of SSDs 12 (4 per system) Drive vendor and model KIOXIA KCM6XRUL7T68 (CM6 Series) Capacity (GB) 7680 SSD information 2.5-inch4 (15mm) PCIe Gen 4.0, NVMe v1.4 Hardware Configuration BIOS Processor Settings: Dell EMC PowerEdge R7525 Logical Processor Enabled Virtualization Technology Enabled IOMMU Support Enabled L1 Stream HW Prefetcher Enabled L2 Stream HW Prefetcher
Load more

Recommended publications
  • Greenplum Database Performance on Vmware Vsphere 5.5
    Greenplum Database Performance on VMware vSphere 5.5 Performance Study TECHNICAL WHITEPAPER Greenplum Database Performance on VMware vSphere 5.5 Table of Contents Introduction................................................................................................................................................................................................................... 3 Experimental Configuration and Methodology ............................................................................................................................................ 3 Test Bed Configuration ..................................................................................................................................................................................... 3 Test and Measurement Tools ......................................................................................................................................................................... 5 Test Cases and Test Method ......................................................................................................................................................................... 6 Experimental Results ................................................................................................................................................................................................ 7 Performance Comparison: Physical to Virtual ......................................................................................................................................
    [Show full text]
  • Setting up Your Dell EMC Powervault ME4 Series Storage System
    c. Remove the enclosure until it reaches the end and hard stops approximately 400 mm expansion enclosure to fail—or be removed—while maintaining access to other 1 Before you begin (15.75 inches). Tighten the mounting screws on the front of the rail kit bracket. enclosures. The middle SAS ports on expansion modules are not used. WARNING: Before you set up and operate your Dell EMC storage system, d. Return the enclosure to the fully home position. review the safety instructions that came with it. 2 0A Unpack storage system equipment 1 Setting Up Your 6 An ME4 Series storage system includes: 0B 3 Dell EMC PowerVault ME4 • Documentation • Expansion cables (1 per expansion module) • 2U or 5U enclosure • Optional enclosure bezel with key (1 per 4 2U enclosure) Series Storage System • Power cables (2) 1A • Separately packaged disk drives (5U • I/O module blank (2U single-controller enclosure only) storage system only) 5 1B • Fibre Channel or iSCSI SFP+ transceivers or • Disk drive blank (if 2U storage system is cables (1 per host port) not fully populated) • Host cables (1 per controller module host port) • Appropriate rackmount kit for 2U or 5U 7 enclosure 2A Develop a configuration plan 2B Before installing the storage hardware, develop a configuration plan where you can 8 record host server information, switch information, and network information. 9 A B C Consider plans for multipath/failover Item Description Item Description Redundancy is provided by multipathing, which allows alternate paths if a data path 1 Front rack post - square hole 6 Clamping screw (B) 9A fails.
    [Show full text]
  • Terms and Conditions for Vmware on IBM Cloud Services
    Terms and Conditions for VMware on IBM Cloud Services These Terms and Conditions for VMware on IBM Cloud Services (the “Terms”) are a legal agreement between you, the customer (“Customer” or “you”), and Dell. For purposes of these Terms, “Dell” means Dell Marketing L.P., on behalf of itself and its suppliers and licensors, or the Dell entity identified on your Order Form (if applicable) and includes any Dell affiliate with which you place an order for the Services. Your purchase of the Services is solely for your internal business use and may not be resold. 1. Your use of the Services reflected on your VMware on IBM Cloud with Dell account and any changes or additions to the VMware on IBM Cloud Services that you purchase from Dell are subject to these Terms, including the Customer Support terms attached hereto as Exhibit A, as well as the Dell Cloud Solutions Agreement located at http://www.dell.com/cloudterms (the “Cloud Agreement”), which is incorporated by reference in its entirety herein. 2. You are purchasing a Subscription to the Services which may include VMware vCenter Server on IBM Cloud or VMware Cloud Foundation on IBM Cloud (individually or collectively, the “Services”). “Subscription” means an order for a quantity of Services for a defined Term. The “Term” is one (1) year from the start date of your Services, and will thereafter automatically renew for successive month to month terms for the duration of your Subscription. 3. The Services will be billed on a monthly basis, with payment due and payable in accordance with the payment terms set forth in the Cloud Agreement.
    [Show full text]
  • Emc Scaleio Design Considerations and Best Practices
    EMC SCALEIO DESIGN CONSIDERATIONS AND BEST PRACTICES ABSTRACT This white paper provides technical information, best practices, and hardware and software design considerations for planning the deployment of ScaleIO June, 2016 WHITE PAPER To learn more about how EMC products, services, and solutions can help solve your business and IT challenges, contact your local representative or authorized reseller, visit www.emc.com, or explore and compare products in the EMC Store Copyright © 2016 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided “as is.” EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. VMware and <insert other VMware marks in alphabetical order; remove sentence if no VMware marks needed. Remove highlight and brackets> are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other trademarks used herein are the property of their respective owners. Part Number HXXXXX <required, see Part numbers below for more info> 2 TABLE
    [Show full text]
  • Vmware Tanzu Greenplum on Azure Marketplace Release Notes V6.5.Pdf
    Azure Marketplace Release Notes v6.5 VMware Tanzu Greenplum Updated: September 2021 ARM template version 6.5 is based on: - VMware Tanzu Greenplum Database version 6.13.0 Or - VMware Tanzu Greenplum Database version 5.28.4 Or - VMware Tanzu Greenplum Database version 4.3.33 Overview VMware Tanzu Greenplum on Azure uses Azure Resource Manager (ARM) template to automate the deployment of a cluster in the Azure cloud. Cloud Native and Cloud Managed Tools and Features Utility/Feature Description bouncer Command line utility that simplifies using pgBouncer connection pooler. gpcompute Grow or shrink compute independently of storage. gpgrow Grow storage independently of compute. gpmaintain / Automates routine maintenance of VMware Tanzu Greenplum such as gpcronmaintain vacuum and analyzing tables. gpoptional Installation tool for installing optional components such as MADlib and Command Center. gppower Automates the Pausing and Resuming a cluster to save on infrastructure costs. gprelease / Automates the upgrade of VMware Tanzu Greenplum, any optional gpcronrelease components installed, and the cloud utilities. gpsnap / Automates the execution of snapshot backups and restores using the cloud gpcronsnap vendor's native snapshot utilities. Self-Healing Automatic instance replacement and recovery in a failure event. VMWare Tanzu Greenplum Azure Marketplace Release Notes v6.5 Licensing Greenplum on Azure BYOL is licensed by the number of cores deployed and it is important to note that in Azure, 1 vCPUs equals 1 core. Customers will total the number of vCPUs deployed in the cluster and then purchase that many subscription cores from VMware Tanzu Software. Calculating Usable Storage To determine the storage size of the Deployment, multiply the number of segment instances in the cluster times the number of disks per instance, and times the size of disk chosen to get the raw storage.
    [Show full text]
  • GOOGLE KUBERNETES ENGINE (GKE) ON-PREM on VMWARE Vsan™ Simplicity, Agility, Resilience, and Performance
    SOLUTION OVERVIEW GOOGLE KUBERNETES ENGINE (GKE) ON-PREM ON VMWARE vSAN™ Simplicity, Agility, Resilience, and Performance Google Cloud’s Anthos on VMware vSAN The Rise of Cloud-Native Applications Digital transformation is driving a new application development and deployment approach called Cloud-native. Cloud-native applications empower your developers by providing the resources and environments they need to deliver applications faster, on-premises or in the cloud, without the need for IT operations intervention. Hyperconverged Infrastructure for Cloud-Native Applications VMware, Hyperconverged Infrastructure (HCI), powered by vSAN™, is the market leader in low cost and high performance next-generation HCI solutions. vSAN delivers TCO reduction benefits over traditional 3-tiered architecture by eliminating infrastructure silos. vSAN also allows customers to achieve infrastructure agility and scalability by converging traditional compute and storage silos onto industry-standard servers, dramatically simplifying operations. VMware vSphere Cloud Provider (VCP) enables dynamic provisioning, easy deployment, upgrade and management for storage of Cloud-native applications. With VMware’s vSphere Cloud Provider, administrators and developers can easily use UNIQUE CAPABILITIES vSAN for both ephemeral and persistent storage for stateless and stateful • Integrate Kubernetes storage classes containerized applications. with VMware Storage Policy Based Management. The storage class definition in Kubernetes maps to policies defined through vSAN Storage Policy Based Management (SPBM) to achieve different levels of SLAs and • Easily scale-out vSAN and Kubernetes QoS and can benefit from advanced vSAN data services features such as clusters. deduplication, compression and checksums. • Protect infrastructure and workload VMs with VMware vSphere® High Availability Why GKE On-Prem on vSAN? and vSAN data services.
    [Show full text]
  • Google Cloud Vmware Engine Simplify Your Journey to the Cloud
    GOOGLE CLOUD VMWARE ENGINE SIMPLIFY YOUR JOURNEY TO THE CLOUD Seamlessly shift workloads from your Introducing Google Cloud VMware Engine datacenter to the cloud with the Google Google Cloud VMware Engine delivers a simple and seamless Cloud VMware Engine way to migrate to the cloud without having to re-architect or refactor applications. With this solution, you can benefit from Industries are transforming and businesses are evolving at flexible, on-demand capacity to rapidly meet business needs a rapid rate. In this environment, owning and operating a and realize cost savings compared to running workloads on- datacenter is not only a competitive disadvantage, but a burden premises. Running your VMware-based workloads in Google as organizations try to keep up with the business and customer Cloud allows you to maintain operational continuity and leverage demands. existing investments and tools, while benefiting from the agility, speed, and automation of the cloud. In fact, 80% of enterprises will have shut down their data center by 20251, and yet migration can still be a complex process. Workloads continue to run on a native VMware SDDC stack Migration from on-premises to cloud environments can be on bare metal, including VMware vSphere, vCenter, vSAN tricky when considering existing processes, tools, and training. and NSX to ensure consistency and compatibility. This allows Application compatibility and consistent security and operational you to migrate, manage, and scale workloads from your data processes are paramount to de-risk your migration and ensure center to the cloud, without refactoring or causing disruption to business continuity. your network, security, or operational policies.
    [Show full text]
  • Integration with Apple School Manager
    Integration with Apple School Manager VMware Workspace ONE UEM Integration with Apple School Manager You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com © Copyright 2021 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 2 Contents 1 Introduction to Apple School Manager Integration 4 2 Apple School Manager Integration 9 3 Apple School Manager Device Distribution 15 4 Apple School Manager One-to-One Device Management 20 5 Apple School Manager Shared Device Management 22 6 View Users of Shared Devices 26 7 Device Enrollment 29 VMware, Inc. 3 Introduction to Apple School Manager Integration 1 As part of Apple Education, Workspace ONE UEM powered by AirWatch provides a configuration called Apple School Manager. To maximize the benefits of the use Apple devices in the classroom, Apple School Manager (ASM) enables you to: n Install an MDM profile on a shared iPad that is not removable. n Provision devices in Supervised mode over-the-air to access extra security and configuration settings. n Create accounts for teachers, students, and staff by connecting to your Student Information System, through bulk import, or manual creation. n Use Managed Apple IDs. n Purchase Apple content and use other Apple Services, such as iTunes U, and managed Apple IDs. This guide helps you integrate Apple School Manager with your existing VMware Workspace ONE UEM deployment, to combine the unique advantages of Workspace ONE UEM device management and Apple School Manager.
    [Show full text]
  • AMD EPYC™ Processors Bring Advanced Security Features and High-Performance Capabilities to Vmware Customers
    September 30, 2020 AMD EPYC™ Processors Bring Advanced Security Features and High-Performance Capabilities to VMware Customers — VMware vSphere® 7.0U1 adds support for AMD Secure Encrypted Virtualization- Encrypted State, enhancing security of data in virtualized environments — — AMD EPYC processors provide up to 2.3x the performance compared to the competition on VMware1 — SANTA CLARA, Calif., Sept. 30, 2020 (GLOBE NEWSWIRE) -- AMD (NASDAQ: AMD) today highlighted the latest expansion of the AMD EPYC™ processor ecosystem for virtualized and hyperconverged infrastructure (HCI) environments with VMware® adding support for AMD Secure Encrypted Virtualization-Encrypted State (SEV-ES) in its newest vSphere® release, 7.0U1. With the latest release, VMware vSphere now enables AMD SEV-ES, which is part ofA MD Infinity Guard, a robust set of modern, hardware enabled features found in all 2nd Gen AMD EPYC processors. In addition to VM memory encryption, SEV-ES also provides encryption of CPU registers and provides VMware customers with easy-to-implement and enhanced security for their environments. “As the modern data center continues to evolve into a virtualized, hybrid cloud environment, AMD and VMware are working together to make sure customers have access to systems that provide high levels of performance on virtualization workloads, while enabling advanced security features that are simple to implement for better protection of data,” said Dan McNamara, senior vice president and general manager, Server Business Unit, AMD. “A virtualized data center with AMD EPYC processors and VMware enables customers to modernize the data center and have access to high-performance and leading-edge security features, across a wide variety of OEM platforms.” “In a virtualized environment, it is critical to have protection of data not only from other virtual machines, but the hypervisor itself.
    [Show full text]
  • Vmware Horizon 7 Datasheet
    DATASHEET VMWARE HORIZON 7 AT A GLANCE End-User Computing Today VMware Horizon® 7 delivers virtualized or Today, end users are leveraging new types of devices for work—accessing hosted desktops and applications through a Windows and Linux applications alongside iOS or Android applications—and single platform to end users. These desktop are more mobile than ever. and application services—including Remote Desktop Services (RDS) hosted apps, In this new mobile cloud world, managing and delivering services to end users packaged apps with VMware ThinApp®, with traditional PC-centric tools have become increasingly di cult. Data loss software-as-a-service (SaaS) apps, and and image drift are real security and compliance concerns. And organizations even virtualized apps from Citrix—can all are struggling to contain costs. Horizon 7 provides IT with a new streamlined be accessed from one digital workspace approach to deliver, protect, and manage Windows and Linux desktops and across devices, locations, media, and applications while containing costs and ensuring that end users can work connections without compromising quality anytime, anywhere, on any device. and user experience. Leveraging complete workspace environment Horizon 7: Delivering Desktops and Applications as a Service management and optimized for the software– defi ned data center, Horizon 7 helps IT control, Horizon 7 enables IT to centrally manage images to streamline management, manage, and protect all of the Windows reduce costs, and maintain compliance. With Horizon 7, virtualized or hosted resources end users want, at the speed they desktops and applications can be delivered through a single platform to end expect, with the e ciency business demands.
    [Show full text]
  • D1.5 Final Business Models
    ITEA 2 Project 10014 EASI-CLOUDS - Extended Architecture and Service Infrastructure for Cloud-Aware Software Deliverable D1.5 – Final Business Models for EASI-CLOUDS Task 1.3: Business model(s) for the EASI-CLOUDS eco-system Editor: Atos, Gearshift Security public Version 1.0 Melanie Jekal, Alexander Krebs, Markku Authors Nurmela, Juhana Peltonen, Florian Röhr, Jan-Frédéric Plogmeier, Jörn Altmann, (alphabetically) Maurice Gagnaire, Mario Lopez-Ramos Pages 95 Deliverable 1.5 – Final Business Models for EASI-CLOUDS v1.0 Abstract The purpose of the business working group within the EASI-CLOUDS project is to investigate the commercial potential of the EASI-CLOUDS platform, and the brokerage and federation- based business models that it would help to enable. Our described approach is both ‘top down’ and ‘bottom up’; we begin by summarizing existing studies on the cloud market, and review how the EASI-CLOUDS project partners are positioned on the cloud value chain. We review emerging trends, concepts, business models and value drivers in the cloud market, and present results from a survey targeted at top cloud bloggers and cloud professionals. We then review how the EASI-CLOUDS infrastructure components create value both directly and by facilitating brokerage and federation. We then examine how cloud market opportunities can be grasped through different business models. Specifically, we examine value creation and value capture in different generic business models that may benefit from the EASI-CLOUDS infrastructure. We conclude by providing recommendations on how the different EASI-CLOUDS demonstrators may be commercialized through different business models. © EASI-CLOUDS Consortium. 2 Deliverable 1.5 – Final Business Models for EASI-CLOUDS v1.0 Table of contents Table of contents ...........................................................................................................................
    [Show full text]
  • Oracle Database Scalability in Vmware® ESX Vmware ESX 3.5
    Performance Study Oracle Database Scalability in VMware® ESX VMware ESX 3.5 Database applications running on individual physical servers represent a large consolidation opportunity. However enterprises considering such consolidation want guidance as to how well databases scale using virtualization. Database workloads are often provisioned on systems with much higher CPU and memory configurations than required by their average utilization. This is most commonly driven by the need for “headroom”—because database workloads are hard to migrate to a larger system, administrators often select a system much larger than immediately required in order to ensure that there will be sufficient capacity for peak portions of the workload and to allow for future growth. As a result, the utilization of dedicated database systems is often less than 20 percent of available CPU. For example, when studying over 2,000 four‐way Oracle database instances, the average utilization was found to be 4.92 percent (from data captured by VMware Capacity Planner, June 2006). In addition, today’s multisocket, multicore systems, with high memory capacity and bandwidth, multiple high‐speed network connections, and numerous high‐performance storage options provide computing resources that are difficult to fully utilize with a single database instance. As a result, there is ample opportunity to consolidate several database instances onto a single server. The tests presented in this paper demonstrate that when scaling out (that is, increasing the number of virtual machines on one physical server) the performance of the Oracle database workloads in each virtual machine remain similar to the performance of the Oracle database workload in a single virtual machine on the same host while ESX CPU utilization scales in a nearly linear fashion.
    [Show full text]