TechRefGuide_PerfTuneVirtual_905605
- 格式：pdf
- 大小：145.17 KB
- 文档页数：12
Epicor 9.05Performance Tuning Guide (Virtual Environment)9.05.605DisclaimerThis document is for informational purposes only and is subject to change without notice. This document and its contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its date of publication. However, Epicor Software Corporation makes no guarantee, representations or warranties with regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a particular purpose, merchantability, satisfactory quality or reasonable skill and care. As each user of Epicor software is likely to be unique in their requirements in the use of such software and their business processes, users of this document are always advised to discuss the content of this document with their Epicor account manager. All information contained herein is subject to change without notice and changes to this document since printing and other important information about the software product are made or published in release notes, and you are urged to obtain the current release notes for the software product. We welcome user comments and reserve the right to revise this publication and/or make improvements or changes to the products or programs described in this publication at any time, without notice. The usage of any Epicor software shall be pursuant to an Epicor end user license agreement and the performance of any consulting services by Epicor personnel shall be pursuant to Epicor's standard services terms and conditions. Usage of the solution(s) described in this document with other Epicor software or third party products may require the purchase of licenses for such other products. Where any software is expressed to be compliant with local laws or requirements in this document, such compliance is not a warranty and is based solely on Epicor's current understanding of such laws and requirements. All laws and requirements are subject to varying interpretations as well as to change and accordingly Epicor cannot guarantee that the software will be compliant and up to date with such changes. All statements of platform and product compatibility in this document shall be considered individually in relation to the products referred to in the relevant statement, i.e., where any Epicor software is stated to be compatible with one product and also stated to be compatible with another product, it should not be interpreted that such Epicor software is compatible with both of the products running at the same time on the same platform or environment. Additionally platform or product compatibility may require the application of Epicor or third-party updates, patches and/or service packs and Epicor has no responsibility for compatibility issues which may be caused by updates, patches and/or service packs released by third parties after the date of publication of this document. Epicor® is a registered trademark and/or trademark of Epicor Software Corporation in the United States, certain other countries and/or the EU. All other trademarks mentioned are the property of their respective owners. Copyright © Epicor Software Corporation 2011. All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of Epicor Software Corporation.9.05.605Revision: May 31, 2011 10:09 a.m.Total pages: 12sys.ditavalContentsIntroduction (4)Virtual Environment Requirements and Recommendations (5)Hardware Requirements (5)Calculate Application Server Requirements (5)Virtual Design Example (6)Storage (6)Network Adapters (7)vCPU Recommendations (7)Memory (7)Network Load Balancing Setup (8)Install NLB (8)Set Up NLB on the First Server (8)Set Up NLB on the Second Server (9)Additional Configuration Settings (10)IntroductionThis Technical Reference Guide explores hardware sizing and Network Load Balancing (NLB) considerations for designing an Epicor application architecture in a virtual environment that supports scalability.The guide is divided into two main parts:•Virtual Environment Requirements and Recommendations•Network Load Balancing SetupImportant This guide is intended for use with Epicor 9.05 or later.Virtual environments provide flexibility and can scale up or down more easily that physical environments. The design approach is more forgiving as it is possible to clone machines and add them to the load balancing pool to accommodate changes in usage patters.Note Epicor recommends that you monitor your NLB environment to ensure that the servers are runningwell. Several third-party applications are available. If the monitor reports show that the servers are workingtoo hard, then that is a good indication that the environment needs more resources. One solution can beto add more virtual application servers into the load balancing pool.Virtual Environment Requirements and RecommendationsThis section explains the requirements for setting up a successful virtual server environment for your Epicor application.Hardware RequirementsThe hardware requirements for a virtual environment are the same as for a physical environment. As virtualenvironments scale up to only 4 or 8 vCPUs (Virtual CPUs), it is mandatory to load balance the virtual application servers.The following are the physical hardware requirements for a 100 user system. These requirements must be reflected in a virtual environment.•Windows 2003 or 2008 Server (64-bit recommended)•SQL Server - 4 CPU sockets filled with XEON Quad or Hex-core ~3.0 Ghz (or better)•Application Server - 4 CPU sockets filled with XEON Hex-core ~3.0 Ghz (or better)•Direct connection between SQL server and application server, < 1 ms ping (no latency)The SQL server should have 8 vCPUs; preferably it should be physical.The virtualization hosts must have the following virtualization features for good performance:•Intel•Intel VT•EPT•AMD•AMD-V•RVI Be sure that all power saving features are turned off on the BIOS level for best performance.Calculate Application Server RequirementsThis topic shows how to calculate the application server requirements for a 100 user environment. As 100 users is close to the top range in the medium environment, the following estimates are based on Hex-core CPUs.4 CPU sockets x 6 cores = 24 cores.Thus, at least 24 cores are required for the Epicor application servers. Divide that value by 4 based on the use of a 4 vCPU virtual application servers.Thus, 6 virtual application servers are required to support around 100 users.Note Printing a report consumes one vCPU so depending on reporting volume, there might be a needfor one or two dedicated reports servers.Virtual Environment Requirements and Recommendations Performance Tuning Guide (Virtual Environment)The preferred way to load balance these application servers is through an F5 Load Balancer. Microsoft Network Load Balancing can be an option as well but it has some limitations.Virtual Design ExampleThe following shows a recommended virtual environment design.This design consists of the following servers:•APP01 to APP06 = Application servers, load balanced through F5 or NLB•REP01 and REP02 = Report servers, load balanced through F5 or NLB•SQLDB01 = SQL server, a physical server following the hardware sizing guide.With this design it is possible to:•Add/remove application and reports servers as needed. It is possible to clone an application or report serverand then add it to either the application or report server load balancing pool when more resources are needed.•Temporarily add more resources for high-volume periods of the year. During year-end more report serverscould be temporarily added to accommodate the need for the higher report volumes. The additional report servers could then be removed or shut down when the year-end activities are over.StoragePlan virtual storage the same as you would for a physical environment.Detailed recommendations:•Use at least RAID 10 - never RAID 5. Create RAID 10 LUNs (Logical Unit Numbers) and then place the virtualmachines on those LUNs.•In vSphere, make sure that the disk provisioning type is set to Thick .•Use the VMware Paravirtual SCSI controller for best performance.Performance Tuning Guide (Virtual Environment)Virtual Environment Requirements and RecommendationsNetwork AdaptersEpicor recommends having many physical network cards attached to each virtualization host, preferably one dedicated physical network card per virtual machine on the host.Detailed requirements:•High bandwidth virtual machines should use NIC (Network Interface Card) teaming - using multiple networkcables/ports in parallel to increase the link speed beyond the limits of any one single cable or port.•In vSphere, use the VMXNET 3 Network Adapter.NoteNote that the E1000 is selected by default so VMXNET 3 is always an active choice.vCPU RecommendationsAvoid giving a virtual machine a high vCPU count, such as eight. High vCPU virtual machines run inefficiently.Instead, set up two virtual machines, each with four vCPUs in a load balanced pool. Make sure that the vCPU to physical core ratio is at least 1:1. Do not over-commit CPU cores.MemoryDisable features like memory ballooning and memory overcommit. Be sure that the virtualization hosts have as much physical RAM as the total allocated to the virtual machines.Virtual Environment Requirements and Recommendations Performance Tuning Guide (Virtual Environment)Network Load Balancing SetupThis section explains how to configure Network Load Balancing in Windows for two Epicor application servers.The example can be extended to add more servers.Install NLBThis task describes how to install NLB. Perform these steps on each Epicor application server that will be part of the load balancing pool.Both servers in the load balancing pool must have at least two network adapters. One adapter will be dedicated to NLB.1.From the Start menu, select Administrative Tools > Server Manager2.Under the server name, click Features .3.Click Add Features .4.In the Add Features Wizard , select the Network Load Balancing check box and click Next .5.Click Install .6.Follow the installation steps and restart the server after the installation is complete.Set Up NLB on the First ServerThis task describes how to create a load balanced environment on the first server.1.From the Start menu, select Administrative Tools > Network Load Balancing Manager.2.From the Cluster menu, select New .3.In the Connect screen, enter the name of the Host that you want to join to the NLB cluster and clickConnect .ExampleEPICORONE4.Select the Interface name that you want to use for NLB and click Next .ExampleLocal Area Connection 2, 192.168.1.25.In Host Parameters screen, accept the default values and click Next .Performance Tuning Guide (Virtual Environment)Network Load Balancing Setup6.In the Cluster IP Address screen, enter the IP address to which an Epicor application client will connect.a.Click Add.b.Enter the IPv4 address and Subnet mask.c.Click OK.Example192.168.1.5IPAddress255.255.255.0Subnetmaskd.Click Next.7.In the Cluster Parameters screen, enter a Full internet name for the cluster.ExampleEPICORNLBRegister the full internet name in your DNS server(s) if you want to connect through the name instead of the IP address.8.For the Cluster operation mode, select Unicast and click Next.9.In the Port Rules screen, define a port rule.a.Click Edit.b.For the Affinity, select None. Epicor is a stateless application.c.Accept all other default values.d.Click OK.10.Click Finish.Set Up NLB on the Second ServerThis task describes how to add the second server to the load balanced environment created on the first server.1.From the Start menu, select Administrative Tools > Network Load Balancing Manager.2.From the Cluster menu, select Connect to Existing.3.In the Host field, enter the host name from the first server and click Connect.ExampleEPICORONENetwork Load Balancing SetupPerformance Tuning Guide (Virtual Environment)4.Click Finish.5.In the Network Load Balancing Clusters tree view, right-click the cluster name and select Add Host toCluster.6.In the Connect screen, enter the name of the Host that you want to join to the NLB cluster and clickConnect.ExampleEPICORTWO7.Select the Interface name that you want to use for NLB and click Next.ExampleLocal Area Connection 2, 192.168.1.48.In the Host Parameters screen, accept the default values and click Next.9.Click Finish.The NLB Cluster is operational when the status of all members appears as Converged in the Network Load Balancing Manager console.Additional Configuration SettingsThe following settings are required in a load balanced environment.ProcessServer and TaskAgent settings:•Run only one ProcessServer and TaskAgent per NLB environment.•Enable the ProcessServer and TaskAgent on one of the Epicor application servers.Client .mfgsys file settings:•The AppServer RL value must point to the NLB IP address. Do not use the NLB cluster name.Example<AppServer URL value="AppServerDC://192.168.1.5:9431" />Set up the following in the System Agent Maintenance program on all servers:•In the Task AppServer section, set the AppServer URL field to the host name of a server in the cluster. Do not use a load balanced IP address.ExampleAppServerDC://EPICORONE•In the System AppServer section, set the AppServer URL field to the load balanced IP address.•Set the Server File Directory and Client File Directory to the same UNC path.Example\\EPICORONE\EpicorDataPerformance Tuning Guide (Virtual Environment)Network Load Balancing Setup•Set the Client Program Directory to the appropriate UNC path.Example\\EPICORONE\Epicor905\Client11Epicor 9.05 | 9.05.605Network Load Balancing Setup Performance Tuning Guide (Virtual Environment)Additional information is available at the Education and Documentation areas of the EPICweb Customer Portal. To access this site, you need a Site ID and an EPICweb account. To create an account, go to .。
