Download
1 / 63
630 likes | 817 Vues
VIR302. Planning for Optimal Management Server Performance and Scalability. Ben Fersenheim App-V Sustained Engineering Microsoft. Introduction. An overview of what’s to come. Session Overview. App-V Management Server Infrastructure.
E N D
VIR302 Planning for Optimal Management Server Performance and Scalability Ben Fersenheim App-V Sustained Engineering Microsoft
Introduction An overview of what’s to come
App-V Management Server Infrastructure A survey of the components of the App-V Management Server
App-V Management Server InfrastructureIn this section we will answer the following • What is the App-V Management Server and what value does it provide? • What are the primary components of the App-V Management Server? • What are the fundamental operations performed by the App-V Management Server?
App-V Management Server InfrastructureValue proposition Applications are isolated • Isolation allows the application to behave consistently regardless of the changes in the OS or other applications in the system • Lowers application testing costs for enterprises Applications are delivered on demand (SaaS) • Brings the benefits of SaaS to rich Windows applications • Applications can be streamed from a variety of locations: locally, IIS server, App-V Server, ConfigMgr Server, or other ESDs and devices Centralized management and servicing • Service in one central location, stream to all users • User based application targeting • Simplified management and deployment of applications to an enterprise
And now, a word from our audience What are the major components that the comprise the App-V management infrastructure? interactive
App-V Management Server InfrastructureManagement Server • Point of service for App-V clients • Windows service • Balances load across cooperating proceses • Scale out across multiple Management Servers
App-V Management Server InfrastructureManagement Web Service • Point of service for the Management Console • Implemented as an ASP.NET web service • Can be deployed independently of the Management Server
App-V Management Server InfrastructureManagement Console • Administrative portal • MMC 3.0 snap-in • Consumer of the Management Web Service • Can be deployed independently
App-V Management Server InfrastructureApp-V SQL Database • Hosts application, package, entitlement, and reporting data • Serves content for Management Server and Management Web Service
App-V Management Server InfrastructureActive Directory • Provides user and group data for entitlements • Read-only
App-V Management Server InfrastructureExternal dependencies • Network load balancers • Software-based NLB • Hardware load balancers • Content directory • Hosts icons, OSD files, and SFT files for client access • Located on a share on or off the Management Server
App-V Management Server InfrastructureOperations • The App-V Management Server performs four fundamental operations • Publishing • Streaming • Metering • Management
Management Server Operations Examining the fundamental operations in more detail
Management Server OperationsIn this section we will • Identify the factors that affect performance and scalability • Examine the fundamental operations performed by the Management Server in more detail
Management Server OperationsPerformance vs. scalability Performance Scalability Change of measurable behavior Sustained rates vs. bursts Throughput vs. bandwidth • Measurable behavior • Focused on end-user tasks • Cumulative effects
Management Server OperationsIntroducing the model (cont.) • A list of the key factors that affect the scalability of the management server infrastructure when performing the operation under study
Management Server OperationsPublishing refresh (cont.) • Overall CPU load on the Management Server • Volume of concurrent requests • Package profile • SQL Server capacity • Entitlement queries • Application catalog retrieval • Content directory latency
Management Server OperationsPackage load (cont.) • FB1-optimized packages • Network load balancing • Auto-load settings
Management Server OperationsApplication launch (cont.) • Disconnected operation modes • Volume of concurrent requests • Network load balancing
Management Server OperationsMetering data upload (cont.) • Volume of data collected • Publishing refresh interval • Application launch frequency • Volume of publishing refreshes • SQL Server capacity • CPU • APPLICATION_USAGE table
Management Server OperationsManagement (cont.) • Package profile • Complexity of operation • Package with 100+ OSDs • Application with 100+ entitlements • SQL Server capacity • Concurrent non-management activity
Guidance Best practices and recommendations to guide deployment planning
GuidanceIn this section • Sample deployment figures • Important configuration parameters • Additional deployment options • Helpful tools • Resources
GuidanceSample deployment figures • Machine specs • Windows Server 2008 • 2x Dual core 3GHz • 4GB RAM • 1 GigE network • Single Management Server • Dedicated SQL Server
GuidanceSample deployment figures Table 1 – Impact of sample operations on App-V Management Server
GuidanceSample deployment figures Table 2 – Impact of sample operations on App-V data store growth
GuidanceUnderstanding your model • Distribution of user load on the system • When do publishing refreshes happen? • What triggers streaming activity? • How many launches per day? • Package and application profile • How many total packages? • Average/max applications per package • Average/max FTAs per package
GuidanceUnderstanding your model (cont.) • Administrative tasks • How frequently are packages deployed? • How frequently do entitlements change? • Can tasks be scheduled off-hours?
GuidanceAdditional deployment options • Streaming Server • File streaming • HTTP streaming • HTTP reporting • SCCM
GuidanceHelpful tools • ADInsight – monitor client-side Active Directory activity • SQL Profiler – collect and analyze traffic • Perfmon – track OS resource usage • Network Monitor – analyze network traffic • VSTT – author and conduct performance tests
