2 Introduction 1 Performance on Hosted Server 1 Figure 1: Real World Performance 1 Benchmarks 2 System configuration used for benchmarks 2 Figure 2a: New tickets per minute on E5440 processors 3 Figure 2b: New tickets per minute on E5530 processors 4 Figure 3a: Effect of the number of records in the database 5 Figure 3b: Effect of the number of records in the database 5 Figure 4a: Number of logins per minute to the End User Interface 5 Figure 4b: New logins per minute to the Staff interface on E5540 processors 6 Figure 5: Effect of the number of logged in users 6 System Requirements 7 Load Balancing 7 Separate database and J2EE servers 7 Multiple database servers 7 Multiple application servers 7 Hyper-Threading Performance 8 Redundancy 8 Performance Analysis 9 Conclusions 10 Agiloft Scalability Agiloft, Inc.
3 This paper reviews Agiloft scalability from the perspective of actual use on a hosted server and benchmarks on standard hardware. This analysis is followed by a discussion of the load that is placed on the system by typical users and a brief summary. The benchmark section is focused on operations that are common in production use, such as logging into the system, creating or updating a record and searching for an existing record, and analyzes how scalability increases with the number of CPU cores. It does not address the time taken to execute infrequent administrative actions such as creating a custom table, since these are intrinsically single threaded and are almost unaffected by the number of processors. Avg Load 9am 5pm Peak Load 9am 5pm Hosted Server with 1512 users Comments: These numbers were obtained from a server configured with dual Xeon X5355 processors, RAID 10 SATA hard drives and 24G RAM with 41 hosted knowledgebases (KB) and an average of ~36 users per KB for a total of 1483 users. The 41 KB s provide a broad cross-section of use patterns and the load remains low throughout the business day. Performance typically starts to degrade once the load reaches a number between 2.5 and 3.5 so this server could support a significant number of additional users. All customers on this particular server are located in North America, so the load is highest between 5am and 5pm PST. A machine that served an even distribution of international customers could support about twice as many users without increasing the peak load. Agiloft Scalability Page 1 Agiloft, Inc.
4 Database: MySQL Hardware: Dual Xeon E5440 processors, 24 G RAM, 3 Seagate SAS drives OS: Suse Linux 11 Agiloft Release: 2008_ r82842 Comments: The Nehalem server processors, released in Q1 2009, are expected to increase performance by 40-80%. SAS hard drives provide ~15% better raw server performance for most operations, but except on high volume systems, this is not noticeable for users accessing the system over the Internet because server-side performance is dwarfed by the 1-2 second Internet delay for each user transaction. Agiloft also supports MS SQL and it provides the same performance as MySQL to within 15%. On average MySQL is slightly faster than MS SQL for most tests/loading conditions. Agiloft Scalability Page 2 Agiloft, Inc.
5 Comments: This test was run on the default Demo KB. Performance will increase or decrease depending upon the size of the ticket, the complexity of the KB structure and the number of active business rules. The time required to edit an existing ticket is typically the same as the time required to create a new one. Customers can run the same test on their hardware by selecting Setup/Performance Test from the admin console. As indicated by figure 3a, the number of records in the database does not have a measurable effect on performance, so a system with dual E5440 processors (8 cores) can generate over 80,000 records per hour until it runs out of disk space. Agiloft Scalability Page 3 Agiloft, Inc.
6 Comments: This test illustrates the performance gains that are available from an alternate hardware configuration of dual i7 processors and dual Intel X25-E SSD hard drives. With hyper-threading turned on, the number of records per minute jumped to As indicated by figure 3a, the number of records in the database does not have a measurable effect on performance, so a system with dual E5530 processors (8 cores) system can generate over 232,000 records per hour until it runs out of disk space. Agiloft Scalability Page 4 Agiloft, Inc.
7 Number of records in database 10,000 < 1 second 1,000,000 < 1 second Comments: Time to find text string in database 10,000,000 < 1 second (see video) These numbers reflect the fact that Agiloft incorporates a database-independent full text search engine. There are operations available only to system administrators, such as performing a mass update of all tickets in the knowledgebase, that will vary linearly with the number of tickets in the database. Number of records in database Time to find text string in attached file 10,000 < 1 second 1,000,000 < 1 second 10,000,000 < 1 second These numbers reflect the fact that Agiloft incorporates a database-independent full text search engine that indexes attached files. Number of active processor cores Number of end user logins per minute Comments: These numbers reflect the number of unique users that may login to the Agiloft end user interface per minute. Comparing with figure 2, we see that when a user logs into the system, it imposes a load comparable to creating a single ticket. As detailed in figure 5, any number of users may be logged into Agiloft and unless they are actively doing something, they do not impose a measurable load on the system. Agiloft Scalability Page 5 Agiloft, Inc.
8 Number of active processor cores Comments: Number of staff logins per minute These numbers reflect the number of unique users that may login to the Agiloft staff interface per minute. As detailed in figure 5, any number of users may be logged into Agiloft and unless they are actively doing something, they do not impose a measurable load on the system. The number of new logins per minute on dual E5530 processors exceeds 1,500. Number of logged in users Time to open a new ticket 100 < 1 second 1,000 < 1 second 10,000 < 1 second 100,000 < 1 second Comments: These numbers were obtained with a browser on the same local network as the server with one active user. When connecting over the Internet a delay of 1 to 2 seconds for network connectivity is typical. While the presence of a logged-in user does not affect performance, users who are actively creating or editing tickets will affect performance once the number of requests approaches the rate per CPU shown in figure 2. If 1,000 users were creating new tickets at the rate of one per user per hour, there would not be a significant performance impact. 1,000 users who were each attempting to create new tickets at the rate of one per user per minute would bring an 8-core system to a crawl. Although the number of logged in users does not directly affect performance unless they are active, it does affect the amount of RAM required by JBoss. Each logged in user uses about 5K of RAM, so a server that is intended to support 100,000 logged-in users would be using 5G RAM to hold the login information in memory. Naturally, this requirement only applies to the number of logged-in users. Users who exist in the database but are not logged in do not use any RAM. Agiloft Scalability Page 6 Agiloft, Inc.
9 Agiloft is built on J2EE architecture for scalability and has been tuned through years of production use. Provided the system is configured with at least 8G of RAM, very little time is spent on I/O and performance depends primarily upon the CPU. Because the system is J2EE based, integer performance and the amount of cache in the CPU have a strong impact on performance and recent generations of the Intel chipset are recommended over Opteron or Sparc processors. Load balancing can be applied at the database level, the application server level and by splitting the J2EE and database servers across different machines. About 55% of CPU resources are spent on Java processes and 45% on database processes. By placing the application server and database on separate machines, it is therefore possible to significantly increase scalability. However, it is important to distinguish between scalability for peak loads and performance under typical loads. Splitting the database and application server across different machines will increase scalability but it also increases the communication delay between the database and application server, so while this method will improve performance under peak-load conditions when all cores are active concurrently, performance under typical load conditions will decrease slightly. The database can be configured to distribute reads among multiple systems, but of course writes must be applied to all systems concurrently. As in the example above, this can increase scalability under peak loads, particularly if the system has an unusually heavy load from SQL read statements, but the introduction of the load balancer overhead will decrease performance under typical loads. An alternative to deploying multiple database servers is to configure the machine with SSD hard drives. These provide read times several times faster than traditional hard drives and seek times an order of magnitude faster, at a price point that is significantly lower than an additional server. Such a configuration not only improves scalability under peak loads, but also improves performance under typical loads. The J2EE architecture can be leveraged to cluster the application server across multiple machines and JSP server instances can also be distributed across multiple machines. However, these both carry a high communications overhead since the cache of each application server or JSP server instance must be synchronized. This is only practicable if the application servers are closely coupled by at least a 1Gps connection and in practice; any performance gain from CPU utilization is swamped by the connection overhead under typical load conditions. If the servers were connected over a WAN, performance would suffer severely. For the above reasons, this method of load balancing is no longer supported. Agiloft Scalability Page 7 Agiloft, Inc.
10 For customers running on the Intel i7 architecture, the re-introduction of hyper-threading provides a compelling alternative to load balancing for distributing the CPU load. Whereas prior generations of hyper-threading did little to improve performance, the increased cache sizes and improved architecture of the i7 processors have radically changed the situation. For example, by turning on hyper-threading on a single i7 920 CPU, the number of new tickets that may be created per minute jumps from 833 to 1,200. A single E5530 processor, with hyper-threading turned on and an SSD hard drive, was benchmarked at 2,134 records per minute. Dual E5530 processors, with SSD hard drives were benchmarked at 3,870 records per minute. For high availability configurations, DRDB provides full redundancy by mirroring the hard drives across multiple machines while heartbeat activates the necessary services on the secondary server if the primary dies. The IP address of the primary server is transferred to the secondary so that it transparently replaces the primary machine and the total service interruption time in the event of catastrophic hardware failure is less than 3 minutes. We have used this configuration with our hosted service for several years and provide pre-configured systems or instructions for configuring your own Linux hardware at no additional charge. This methodology can be used if the secondary machine is located at a different facility; however DRDB proxy should be used in this case. In addition to the application server redundancy detailed above, the infrastructure at the co-location facility is configured for high-availability as detailed below: The Ethernet drop to the central switch is redundant and configured for hot-swap failover in the event that the co-location facility's router should fail. The server blades are redundant and are connected via ISCSI to a hot-swap redundant file servers. The file servers are configured with redundant power supplies and RAID 10 hard drives with hot-swap spares. The blade server and file servers use EEC RAM. The firewalls are redundant and configured for hot-swap failover. The central switch is redundant and configured for hot-swap failover. All components are subject to active monitoring and connected to remote power supplies. Agiloft Scalability Page 8 Agiloft, Inc.
11 System resources are only used when the user actually does something, such as creating or editing a record. As is typical for HTML based web products, the "overhead" from passive users is almost zero. For example, when users are filling out a web form, they are entirely passive from the perspective of the system and only become active on clicking the Finish button. This is important because it means that performance is not based on "how many users" there are, but "how many tickets those users are creating/editing per minute". The average member of a sales team or support staff works on 3-8 records per day. If we assume that all users are at the top end of this range and work on 8 records per day, we would expect a sales/support staff with 1,000 full time agents to generate or edit 8,000 records per day, significantly less than our entry level system can handle in half an hour. Of course, it is necessary to add a safety factor for sudden peak loads, and ideally CPU utilization should be less than 25%, so we recommend quad CPU configurations for such customers. This analysis is based on typical configurations, but the system supports creation of an unlimited number of business rules, each of which runs in the foreground or as a scheduled background task to call external scripts, generate s, update related records and carry out other operations necessary to automate the business. The overhead from such processes can be significant, so for very large companies with highly sophisticated business rules, we support the IBM P-Series with up to 64 processors. Although it is unlikely that an enterprise will actually need more than a couple of machine configured with dual Intel X5560 CPU's, support for the P-Series guarantees that plenty of headroom is available if the need arises. Another aspect of scalability is the size of knowledgebase that can be supported while maintaining good performance. For common operations such as finding records containing certain text and editing them, scalability is almost unlimited. The following video demonstrates searching a table containing over 10,000,000 user records for some text (17 such records are found), editing one of them and saving the result. From usage analysis on our ASP servers, we know that about 50% of CPU resources are spent submitting new records such as tickets and s or editing existing ones, 20% is spent generating charts/reports, 15% is spent searching for information and 15% is spent on miscellaneous tasks such as changing tabs, logging in, viewing history information, creating saved searches, changing views, etc. Agiloft Scalability Agiloft, Inc.
12 As detailed in figures 2a and 2b, for systems with two or more CPU cores, throughput increases by a factor of 1.5 to 1.9 each time that the number of active CPU cores is doubled. This is within 25% of the theoretical maximum scalability of 2 and indicates that the system is free of bottlenecks. As detailed in figures 3a, 3b, and 5, testing with over 10,000,000 records and 100,000 active users demonstrates that the number of records and the number of concurrent users does not place a measurable load on the system. Performance is only affected by the number of records that are actually being edited at any one time. Subject to the points raised in the Performance Analysis section, Agiloft can handle creation of over 3,800 tickets per minute on a system configured with dual E5530 CPU s, and can handle creation of over 1,320 tickets per minute on a system configured with dual Xeon E5440 CPU's, regardless of the number of logged in users or existing tickets. For very high load systems, capable of handling over 3,000 tickets per minute, we therefore recommend dual i7 CPU s, such as E5530 s coupled with SSD hard drives. For high availability, we recommend use of a hot-swap redundant server with replication and failover provided by DRDB and heartbeat. Agiloft, Inc. (www.agiloft.com) is a trusted provider of agile business process software. Our unique platform enables our pre-built and custom applications to be tailored to your exact needs without writing custom code, so deployment times and costs are a fraction of other systems. Our design experts ensure success with a full range of services, and the system can be deployed on our cloud infrastructure or on premise. Agiloft offers the most flexible and cost-effective integrated solution for managing complex business processes. Hundreds of customers, from startups to Fortune 100 companies, are using Agiloft to manage their Service Desk, Assets, Repairs, Contracts, Changes, Billing, CRM, SOX Compliance, and dozens of other custom processes. Agiloft Scalability Page 10 Agiloft, Inc.
Sage CRM Technical Specification Client Software This document outlines the recommended minimum software and hardware requirements for running Sage CRM. Please note that while this document refers to Sage
Sage CRM Technical Specification Client Software This document outlines the recommended minimum software and hardware requirements for running Sage CRM. Please note that while the document refers to Sage
JBoss Seam Performance and Scalability on Dell PowerEdge 1855 Blade Servers Dave Jaffe, PhD, Dell Inc. Michael Yuan, PhD, JBoss / RedHat June 14th, 2006 JBoss Inc. 2006 About us Dave Jaffe Works for Dell
Sage CRM Technical Specification Client Software This document outlines the recommended minimum software and hardware requirements for running Sage CRM. Please note that while the document refers to Sage
MEASURING WORKLOAD PERFORMANCE IS THE INFRASTRUCTURE A PROBLEM? Ashutosh Shinde Performance Architect email@example.com Validating if the workload generated by the load generating tools is applied
Cloud Based Application Architectures using Smart Computing How to Use this Guide Joyent Smart Technology represents a sophisticated evolution in cloud computing infrastructure. Most cloud computing products
Parallels Cloud Storage White Paper Performance Benchmark Results www.parallels.com Table of Contents Executive Summary... 3 Architecture Overview... 3 Key Features... 4 No Special Hardware Requirements...
Scaling Database Performance in Azure Results of Microsoft-funded Testing Q1 2015 2015 2014 ScaleArc. All Rights Reserved. 1 Test Goals and Background Info Test Goals and Setup Test goals Microsoft commissioned
White Paper Recording Server Virtualization Prepared by: Mike Sherwood, Senior Solutions Engineer Milestone Systems 23 March 2011 Table of Contents Introduction... 3 Target audience and white paper purpose...
Whitepaper Consolidation EXECUTIVE SUMMARY At this time of massive and disruptive technological changes where applications must be nimbly deployed on physical, virtual, and cloud infrastructure, Red Hat
Agenda Enterprise Performance Factors Overall Enterprise Performance Factors Best Practice for generic Enterprise Best Practice for 3-tiers Enterprise Hardware Load Balancer Basic Unix Tuning Performance
StarWind iscsi SAN: Configuring Global Deduplication May 2012 TRADEMARKS StarWind, StarWind Software, and the StarWind and StarWind Software logos are trademarks of StarWind Software that may be registered
Research Report The Mainframe Virtualization Advantage: How to Save Over Million Dollars Using an IBM System z as a Linux Cloud Server Executive Summary Information technology (IT) executives should be
Enabling Technologies for Distributed Computing Dr. Sanjay P. Ahuja, Ph.D. Fidelity National Financial Distinguished Professor of CIS School of Computing, UNF Multi-core CPUs and Multithreading Technologies
Dell Virtual Remote Desktop Reference Architecture Technical White Paper Version 1.0 July 2010 THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES.
Identifying the Hidden Risk of Data De-duplication: How the HYDRAstor Solution Proactively Solves the Problem October, 2006 Introduction Data de-duplication has recently gained significant industry attention,
bla bla OPEN-XCHANGE Open-Xchange Hardware Needs OPEN-XCHANGE: Open-Xchange Hardware Needs Publication date Wednesday, 8 January version. . Hardware Needs with Open-Xchange.. Overview The purpose of this
v7.1 Technical Specification Copyright 2011 Sage Technologies Limited, publisher of this work. All rights reserved. No part of this documentation may be copied, photocopied, reproduced, translated, microfilmed,
Virtual SAN Design and Deployment Guide TECHNICAL MARKETING DOCUMENTATION VERSION 1.3 - November 2014 Copyright 2014 DataCore Software All Rights Reserved Table of Contents INTRODUCTION... 3 1.1 DataCore
WHITE PAPER FUJITSU PRIMERGY AND PRIMEPOWER SERVERS Performance Comparison of Fujitsu PRIMERGY and PRIMEPOWER Servers CHALLENGE Replace a Fujitsu PRIMEPOWER 2500 partition with a lower cost solution that
Developing a dynamic, real-time IT infrastructure with Red Hat integrated virtualization www.redhat.com Table of contents Introduction Page 3 Benefits of virtualization Page 3 Virtualization challenges
Step-by-Step Guide to configure on Intel Server Systems R2224GZ4GC4 Software Version: DSS ver. 7.00 up01 Presentation updated: April 2013 www.open-e.com 1 www.open-e.com 2 TECHNICAL SPECIFICATIONS OF THE
REDCENTRIC INFRASTRUCTURE AS A SERVICE SERVICE DEFINITION SD021 V2.2 Issue Date 01 July 2014 1) OVERVIEW Redcentric s Infrastructure as a Service (IaaS) enables the to consume server, storage and network
IBM SPSS Statistics Server Understanding the Benefits of IBM SPSS Statistics Server Contents: 1 Introduction 2 Performance 101: Understanding the drivers of better performance 3 Why performance is faster
Propalms TSE Deployment Guide Version 7.0 Propalms Ltd. Published October 2013 Overview This guide provides instructions for deploying Propalms TSE in a production environment running Windows Server 2003,
Best Practices for Deploying SSDs in a Microsoft SQL Server 2008 OLTP Environment with Dell EqualLogic PS-Series Arrays Database Solutions Engineering By Murali Krishnan.K Dell Product Group October 2009
An Oracle White Paper November 2010 Oracle Real Application Clusters One Node: The Always On Single-Instance Database Executive Summary... 1 Oracle Real Application Clusters One Node Overview... 1 Always
Dell EqualLogic Best Practices Series Reference Architecture for a Virtualized SharePoint 2010 Document Management Solution A Dell Technical White Paper Storage Infrastructure and Solutions Engineering
NEC Corporation of America Intro to High Availability / Fault Tolerant Solutions 1 NEC Corporation Technology solutions leader for 100+ years Established 1899, headquartered in Tokyo First Japanese joint
Zadara Storage Cloud A whitepaper @ZadaraStorage Zadara delivers two solutions to its customers: On- premises storage arrays Storage as a service from 31 locations globally (and counting) Some Zadara customers
Performance brief for IBM WebSphere Application Server.0 with VMware ESX.0 on HP ProLiant DL0 G server Table of contents Executive summary... WebSphere test configuration... Server information... WebSphere
Hardware Recommendations Alpha Anywhere is a Windows based system that will run on various Windows versions. The minimum requirement is Windows XP SP3 or Server 2003. However, it is recommended that at
Muse Server Sizing 18 June 2012 Document Version 0.0.1.9 Muse 184.108.40.206 Notice No part of this publication may be reproduced stored in a retrieval system, or transmitted, in any form or by any means, without
White Paper Cisco Prime Home 5.0 Minimum System Requirements (Standalone and High Availability) White Paper July, 2012 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public
STINGRAY TRAFFIC MANAGER SIZING GUIDE 1 Stingray Traffic Manager Sizing Guide Stingray Traffic Manager version 8.0, December 2011. For internal and partner use. Introduction The performance of Stingray
Arista 10 Gigabit Ethernet Switch Lab-Tested with Panasas ActiveStor Parallel Storage System Delivers Best Results for High-Performance and Low Latency for Scale-Out Cloud Storage Applications Introduction
July 2009 About this guide Edition notice This edition applies to Version 4.0 of the Pivot3 RAIGE Operating System and to any subsequent releases until otherwise indicated in new editions. Notification
Capacity Estimation for Linux Workloads Session L985 David Boyes Sine Nomine Associates 1 Agenda General Capacity Planning Issues Virtual Machine History and Value Unique Capacity Issues in Virtual Machines
System Requirements Contents System Requirements... 2 Supported Operating Systems and Databases...2 Features with Additional Software Requirements... 2 Hardware Requirements... 4 Database Prerequisites...
HyperQ Hybrid Flash Storage Made Easy White Paper Parsec Labs, LLC. 7101 Northland Circle North, Suite 105 Brooklyn Park, MN 55428 USA 1-763-219-8811 www.parseclabs.com firstname.lastname@example.org email@example.com
HP Proliant BL460c G7 The HP Proliant BL460c G7, is a high performance, fully fault tolerant, nonstop server. It s well suited for all mid-level operations, including environments with local storage, SAN
Cisco, Citrix, Microsoft, and NetApp Deliver Simplified High-Performance Infrastructure for Virtual Desktops Greater Efficiency and Performance from the Industry Leaders Citrix XenDesktop with Microsoft
Deployment Guide How to prepare your environment for an OnApp Cloud deployment. Document version 1.07 Document release date 28 th November 2011 document revisions 1 Contents 1. Overview... 3 2. Network
Citrix VDI-in-a-Box How to size your VDI-in-a-Box infrastructure Basics of a VDI-in-a-Box grid Simple to install and use Off-the-shelf servers with DAS(direct attached storage) Servers can be of different
SCHOONER WHITE PAPER Top 10 Reasons why MySQL Experts Switch to SchoonerSQL - Solving the common problems users face with MySQL About Schooner Information Technology Schooner Information Technology provides
Introduction By leveraging the inherent benefits of a virtualization based platform, a Microsoft Exchange Server 2007 deployment on VMware Infrastructure 3 offers a variety of availability and recovery
Business white paper HP Process Automation Version 7.0 Server performance Table of contents 3 Summary of results 4 Benchmark profile 5 Benchmark environmant 6 Performance metrics 6 Process throughput 6
SERENA SOFTWARE Scaling for the Enterprise Authors: Bill Weingarz, Pete Dohner, Kartik Raghavan, Amitav Chakravartty 2012-06-11 Table of Contents Who Should Read This Paper?... 3 Introduction... 3 Architecture...
Very Large Enterprise Network, Deployment, 25000+ Users Websense software can be deployed in different configurations, depending on the size and characteristics of the network, and the organization s filtering
High Availability & Disaster Recovery Development Project Concepts, Design and Implementation High Availability & Disaster Recovery Development Project CONCEPTS Who: Schmooze Com Inc, maintainers, core
Very Large Enterprise Network Deployment, 25,000+ Users Websense software can be deployed in different configurations, depending on the size and characteristics of the network, and the organization s filtering
SERENA SOFTWARE Scaling for the Enterprise Authors: Bill Weingarz, Pete Dohner, Kartik Raghavan, Amitav Chakravartty 2012-05-07 Table of Contents Who Should Read This Paper?... 3 Introduction... 3 Architecture...
MS EXCHANGE SERVER ACCELERATION IN VMWARE ENVIRONMENTS WITH SANRAD VXL Dr. Allon Cohen Eli Ben Namer firstname.lastname@example.org 1 EXECUTIVE SUMMARY SANRAD VXL provides enterprise class acceleration for virtualized
1 POSIX and Object Distributed Storage Systems Performance Comparison Studies With Real-Life Scenarios in an Experimental Data Taking Context Leveraging OpenStack Swift & Ceph by Michael Poat, Dr. Jerome
Pivot3 Reference Architecture for VMware View Version 1.03 January 2012 Table of Contents Test and Document History... 2 Test Goals... 3 Reference Architecture Design... 4 Design Overview... 4 The Pivot3
Performance & Scalability of SAS Business Analytics on an NEC Express5800/A1080a (Intel Xeon 7500 series-based Platform) using Red Hat Enterprise Linux 5 SAS Business Analytics Base SAS for SAS 9.2 Red
Using EonStor FC-host Storage Systems in VMware Infrastructure 3 and vsphere 4 Application Note Abstract This application note explains the configure details of using Infortrend FC-host storage systems
#1 HyperConverged Appliance for SMB and ROBO StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with MARCH 2015 TECHNICAL PAPER Trademarks StarWind, StarWind Software and the
Centrata IT Management Suite 3.0 Technical Operating Environment April 9, 2004 Centrata Incorporated Copyright 2004 by Centrata Incorporated All rights reserved. April 9, 2004 Centrata IT Management Suite
An Oracle White Paper December 2011 Oracle Virtual Desktop Infrastructure: A Design Proposal for Hosted Virtual Desktops Introduction... 2! Design Goals... 3! Architectural Overview... 5! Logical Architecture...
EMC Perspective Integrated Grid Solutions from SAS, EMC Isilon and Greenplum Introduction Intensifying competitive pressure and vast growth in the capabilities of analytic computing platforms are driving
Virtualizing Microsoft SQL Server 2008 on the Hitachi Adaptable Modular Storage 2000 Family Using Microsoft Hyper-V Implementation Guide By Eduardo Freitas and Ryan Sokolowski February 2010 Summary Deploying
Cloud computing is a marketing term that means different things to different people. In this presentation, we look at the pros and cons of using Amazon Web Services rather than setting up a physical server
ENTERPRISE STORAGE WITH THE FUTURE BUILT IN Breakthrough Efficiency Intelligent Storage Automation Single Platform Scalability Real-time Responsiveness Continuous Protection Storage Controllers Storage
How to Choose your Red Hat Enterprise Linux Filesystem EXECUTIVE SUMMARY Choosing the Red Hat Enterprise Linux filesystem that is appropriate for your application is often a non-trivial decision due to
SiteCelerate white paper Arahe Solutions SITECELERATE OVERVIEW As enterprises increases their investment in Web applications, Portal and websites and as usage of these applications increase, performance
Seradex White Paper A Discussion of Issues in the Manufacturing OrderStream Microsoft SQL Server High Performance for Your Business Executive Summary Microsoft SQL Server is the leading database product
Dragon NaturallySpeaking and citrix A White Paper from Nuance Communications March 2009 Introduction As the number of deployed enterprise applications increases, organizations are seeking solutions that
W H I T E P A P E R S O L U T I O N : D I S A S T E R R E C O V E R Y T E C H N O L O G Y : R E M O T E R E P L I C A T I O N Disaster Recovery Strategies: Business Continuity through Remote Backup Replication
Sawmill Log Analyzer Best Practices!! Page 1 of 6 Sawmill Log Analyzer Best Practices! Sawmill Log Analyzer Best Practices!! Page 2 of 6 This document describes best practices for the Sawmill universal
Objectives At the end of this chapter, participants will be able to understand: Web server management options provided by Network Deployment Clustered Application Servers Cluster creation and management