Medium Profile Performance Testing FIM Synchronization

Updated: August 10, 2010

Applies To: Forefront Identity Manager, Forefront Identity Manager 2010

The medium organization profile for this initial FIM 2010 R2 Synchronization performance test is described in the following table.

 

Scale Topology Hardware  
  • Single forest

  • 50,000 users

  • 50,000 groups

  • Average of 20 users per group

  • Three servers

  • FIM 2010 R2 Synchronization Service and FIM 2010 R2 Synchronization database collocated on one server

  • FIM 2010 R2 Portal, FIM 2010 R2 Service collocated on one server

  • FIM 2010 R2 Service database

SQL Server database servers have the same hardware.

  • 16-GB SDRAM

  • Four quad-core processors

  • Hard disk volumes:

    • Single volume and spindle for the operating system

    • Single volume and spindle for log files

    • Single volume with four spindles in a RAID 10 configuration for data

Server hosting FIM 2010 R2 Service and FIM 2010 R2 Portal hardware

  • 4-GB SDRAM

  • Single (quad-core) processor

  • Single hard disk volume with one spindle

The tests and results shown in the following table were performed using legacy provisioning. As with the previous test, the Active Directory management agent was connected to a single Active Directory forest and the File management agent exported the provisioned users to a file. Similarly, the Active Directory Management Agent import was performed from a file instead of from an actual Active Directory database. This was done to avoid introducing network delays into the test environment. You should consider the effect of delays based on the network traffic specific to the organization in which you are implementing FIM 2010 when estimating synchronization performance.

 

Operation Elapsed time (hours:minutes:seconds) Statistics Rate

Active Directory management agent full import

00:19:01

Staging

  • Unchanged: 3,190

  • Adds: 100,030

69 objects read/second

Active Directory management agent full synchronization

01:10:26

Inbound synchronization

  • Projections: 99,991

  • Disconnectors: 30

  • Connectors with flow updates: 99,991

Outbound synchronization File management agent

  • Export attribute flow: 99,991

  • Provisioning adds: 99,991

Outbound synchronization FIM 2010 R2 management agent

  • Export attribute flow: 99,991

Provisioning adds: 99,991

23 objects synchronized/second

File management agent export

00:14:09

Adds: 99,993

Updates: 21,488

95 objects exported/second

File management agent delta import

00:20:02

Staging

  • Adds: 99,993

  • 21,488

94 objects read/second

Active Directory management agent delta import

00:12:22

Staging

  • Adds: 2,500

  • Updates: 5,000

  • Deletes: 2,500

3 objects read/second

Active Directory management agent delta synchronization

00:39:44

Inbound synchronization

  • Projections: 2,500

  • Disconnectors: 30

  • Connectors with flow updates: 8,574

  • Connectors without flow updates: 17,341

  • Deleted connectors: 2,500

  • Metaverse object deletes: 2,500

Outbound synchronization FIM 2010 R2 management agent

  • Export attribute flow: 24,735

  • Provisioning adds: 2,500

  • Provisioning disconnects: 2,500

Outbound synchronization File management agent

  • Export attribute flow: 24,133

  • Provisioning adds: 2,500

  • Provisioning disconnects: 2,500

11 objects synchronized/second

File management agent export

00:01:13

Export

  • Adds: 2,500

  • Updates: 21,633

  • Deletes: 2,500

126 objects exported/second

File management agent delta import

00:09:25

Staging

  • Adds: 2,500

  • Updates: 21,634

  • 2,500

47 objects read/second

Community Additions

ADD
Show: