1 / 63

Planning for Optimal Management Server Performance and Scalability

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.

ostinmannual
Download Presentation

Planning for Optimal Management Server Performance and Scalability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VIR302 Planning for Optimal Management Server Performance and Scalability Ben Fersenheim App-V Sustained Engineering Microsoft

  2. Introduction An overview of what’s to come

  3. Session Overview

  4. App-V Management Server Infrastructure A survey of the components of the App-V Management Server

  5. 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?

  6. 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

  7. And now, a word from our audience What are the major components that the comprise the App-V management infrastructure? interactive

  8. App-V Management Server InfrastructureMajor components

  9. App-V Management Server InfrastructureArchitectural diagram

  10. 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

  11. 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

  12. App-V Management Server InfrastructureManagement Console • Administrative portal • MMC 3.0 snap-in • Consumer of the Management Web Service • Can be deployed independently

  13. App-V Management Server InfrastructureApp-V SQL Database • Hosts application, package, entitlement, and reporting data • Serves content for Management Server and Management Web Service

  14. App-V Management Server InfrastructureActive Directory • Provides user and group data for entitlements • Read-only

  15. 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

  16. App-V Management Server InfrastructureOperations • The App-V Management Server performs four fundamental operations • Publishing • Streaming • Metering • Management

  17. Management Server Operations Examining the fundamental operations in more detail

  18. 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

  19. 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

  20. Management Server OperationsWhat affects scalability?

  21. Management Server OperationsIntroducing the model

  22. Management Server OperationsIntroducing the model (cont.)

  23. 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

  24. Management Server OperationsPublishing refresh

  25. Management Server OperationsPublishing refresh (cont.)

  26. 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

  27. Management Server OperationsPackage load

  28. Management Server OperationsPackage load (cont.)

  29. Management Server OperationsPackage load (cont.) • FB1-optimized packages • Network load balancing • Auto-load settings

  30. Management Server OperationsApplication launch

  31. Management Server OperationsApplication launch (cont.)

  32. Management Server OperationsApplication launch (cont.) • Disconnected operation modes • Volume of concurrent requests • Network load balancing

  33. Management Server OperationsMetering data upload

  34. Management Server OperationsMetering data upload (cont.)

  35. 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

  36. Management Server OperationsManagement

  37. Management Server OperationsManagement (cont.)

  38. Management Server OperationsManagement (cont.) • Package profile • Complexity of operation • Package with 100+ OSDs • Application with 100+ entitlements • SQL Server capacity • Concurrent non-management activity

  39. Guidance Best practices and recommendations to guide deployment planning

  40. GuidanceIn this section • Sample deployment figures • Important configuration parameters • Additional deployment options • Helpful tools • Resources

  41. GuidanceSample deployment figures • Machine specs • Windows Server 2008 • 2x Dual core 3GHz • 4GB RAM • 1 GigE network • Single Management Server • Dedicated SQL Server

  42. GuidanceSample deployment figures Table 1 – Impact of sample operations on App-V Management Server

  43. GuidanceSample deployment figures Table 2 – Impact of sample operations on App-V data store growth

  44. 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

  45. GuidanceUnderstanding your model (cont.) • Administrative tasks • How frequently are packages deployed? • How frequently do entitlements change? • Can tasks be scheduled off-hours?

  46. GuidanceImportant client configuration points

  47. GuidanceImportant server configuration points

  48. GuidanceImportant server configuration points (cont.)

  49. GuidanceAdditional deployment options • Streaming Server • File streaming • HTTP streaming • HTTP reporting • SCCM

  50. 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

More Related