mms 2013: configuring service manager for performance and scale

Post on 13-Mar-2016

225 Views

Category:

Documents

2 Downloads

Preview:

Click to see full reader

DESCRIPTION

Concurrency Infrastructure Practice Lead, Nate Lasnoski, presented this material at the Microsoft Management Summit (MMS) in April 2013, in Las Vegas, NV. Lasnoski discusses configuration changes, tools, and strategies for improving the performance and scalability of the System Center Service Manager installation. Audio for this presentation is included after the last slide, in the embedded video. For more information http://www.concurrency.com

TRANSCRIPT

SD-B312

Experiences with Service Manager and Orchestrator

What does performance mean?

What does scale mean?

Agenda

Assumptions for Large Scale Deployments

Hardware Recommendations for Large Scale

Hardware Recommendations for Large Scale

Example Architecture for 50,000+ Users Orchestrator

Runbook Servers

OrchestratorManagement

SM Management Servers

SM Connection Servers

SM Portal SharePoint / WCS

SM Orchestrator Server

SM ORCH Target Server

Service Manager DBSQL 2012

Datawarehouse DBSQL 2012

Windows Server 201224 – 48 vCPUs, 32 – 192 GB RAM

80 GB OS, 600 GB Data

Windows Server 20124 – 8 vCPUs, 8 – 16 GB RAM

60 GB OS, 1 TB+ Data2-4TB of disk for 1095 days

DR: RTO 24 hours

Windows Server 20122 vCPUs, 8 GB RAM

80 GB OSScale number as

workloads demandRTO: 30 min?

Windows Server 20128 vCPUs, 16 GB RAM

60 GB OSScale as workload demands

RTO: 15 min

Windows Server 20124 vCPUs, 8 – 16 GB RAM

60 GB OSDR: RTO 24 hours

Windows Server 20124 – 8 vCPUs, 8 - 16 GB RAM

60 GB OS80-100 concurrent sessions/server

DR: RTO 30 minutes

Windows Server 20124 vCPUs, 16 GB RAM

First is failover for PrimaryScale as workloads demand

RTO: Globally Coninuously Available?

Windows Server 20124 vCPUs, 16 GB RAM

60 GB OSRTO: Not clear

Windows Server 20124 vCPUs, 16 GB RAM

First is failover for PrimaryScale as workloads demand

RTO: Globally Coninuously Available?

Windows Server 20122 vCPUs, 8 GB RAM

80 GB OSScale number as

workloads demandRTO: 30 min?

Service Manager DBSQL 2012

Windows Server 201224 – 48 vCPUs, 32 – 192 GB RAM

80 GB OS, 600 GB Data

Windows Server 20128 vCPUs, 16 GB RAM

60 GB OSScale as workload demands

RTO: 15 min

Windows Server 20128 vCPUs, 16 GB RAM

60 GB OSScale as workload demands

RTO: 15 min

Active DirectorySCOM, SCCM,Other Systems

SQL Server Configuration

SQL Server Configuration

Max Degree of Parallelism

SQL Performance for ServiceManager DB

SQL Logs and Recovery Model

High Availability

Pick the Right User Experience

Console Optimization

View Optimization

Scoped User Roles vs. Non-Scoped

Portal Performance

Portal Performance

Dedicated Servers

Workflow Tweaks

Group Calculation Interval

Troubleshooting Performance Delays

Orchestrator

Orchestrator

Orchestrator

Connector Configuration

Connector Configuration

Workflow / Connector Scheduling

Batch Size

Orchestrator Topologies and Service Manager

Orchestrator Topologies and Service Manager

Orchestrator Topologies and Service Manager

DW and SQL Performance

Configure Transform Batch Size

Top Tweeted Questions

Complete your session evaluations today and enter to win prizes daily. Provide your feedback at a CommNet kiosk or log on at www.2013mms.com.Upon submission you will receive instant notification if you have won a prize. Prize pickup is at the Information Desk located in Attendee Services in the Mandalay Bay Foyer. Entry details can be found on the MMS website.

Resources

For more information: www.concurrency.com

top related