2.2 System Sizing for Single-Node Deployment

2.2.1 System Sizing for a Small Workload

This section helps you in determining whether your environment might meet the requirements for a small workload environment. It provides guidance for hardware requirements and tuning the performance of the workload. You might compare this information with the guidance for medium and large workloads.

Workload Distribution for a Small Workload

The following table provides an example of how identity governance activities might occur in a small workload:

Application

Category

Expected Workload

Identity Governance

Identities

Deltas (per day)

5,000

10,000

Identity Manager

Identities

Events per second

5,000

10

Identity Intelligence (total workload)

Identities

Transactions (per day)

Views (concurrent)

10,000

20,000

5

System Sizing for a Small Workload

Category

Requirement

Cluster node (master+worker)

1

CPU cores (per node)

8

RAM (per node)

32

Disks (per node)

2

Storage per day (1x)

350 MB

Total disk space (365 days)

500 GB

Database Resource Pools Tuning for a Small Workload

Category

Property

Value

Database

active_partitions

tm_concurrency

tm_memory

3

4

2,000

Resource pools

ingest_pool_memory_size

mf_entity_ingest_pool_memory_size

mf_entity_ingest_pool_planned_concurrency

10%

10%

4

Scheduler

plannedconcurrency

tm_memory_usage

maxconcurrency

3

2,000

4

Transformation Hub Tuning for a Small Workload

Property

Quantity

# of Kafka broker nodes in the Kafka cluster

1

# of ZooKeeper nodes in the ZooKeeper cluster

1

# of Partitions assigned to each Kafka Topic

1

# of replicas assigned to each Kafka Topic

1

# of message replicas for the __consumer_offsets Topic

1

Schema Registry nodes in the cluster

1

Kafka nodes required to run Schema Registry

1

# of CEF-to-Avro Stream Processor instances to start

1

2.2.2 System Sizing for Medium Workload

This section helps you in determining whether your environment meets the requirements for a medium workload environment. It provides guidance for hardware requirements and tuning the performance of the workload. You might compare this information with the guidance for small and large workloads.

Workload Distribution for a Medium Workload

The following table provides an example of how identity governance activities might occur in a medium workload:

Application

Category

Expected Workload

Identity Governance

Identities

Accounts

Groups

Entitlements / permissions

Deltas (per day)

25,000

50,000

7,500

7,500

200,000

Identity Manager

Identities

Events per second

25,000

12

Identity Intelligence (total workload)

Identities

Transactions (per day)

Views (concurrent)

50,000

100,000

5

System Sizing for a Medium Workload

Category

Requirement

Cluster node (master+worker)

1

CPU cores (per node)

8

RAM (per node)

48

Disks (per node)

2

Storage per day (1x)

950 MB

Total disk space (365 days)

1 TB

Database Resource Pools Tuning for a Medium Workload

Category

Property

Value

Database

active_partitions

tm_concurrency

tm_memory

4

5

4,000

Resource pools

ingest_pool_memory_size

mf_entity_ingest_pool_memory_size

mf_entity_ingest_pool_planned_concurrency

10%

30%

12

Scheduler

plannedconcurrency

tm_memory_usage

maxconcurrency

4

4,000

5

Transformation Hub Tuning for a Medium Workload

Property

Quantity

# of Kafka broker nodes in the Kafka cluster

1

# of ZooKeeper nodes in the ZooKeeper cluster

1

# of Partitions assigned to each Kafka Topic

3

# of replicas assigned to each Kafka Topic

1

# of message replicas for the __consumer_offsets Topic

1

Schema Registry nodes in the cluster

1

Kafka nodes required to run Schema Registry

1

# of CEF-to-Avro Stream Processor instances to start

1

2.2.3 System Sizing for Large Workload

This section helps you in determining whether your environment might meets the requirements for a large workload environment. It provides guidance for hardware requirements and tuning the performance of the workload. You might compare this information with the guidance for small and medium workloads.

Workload Distribution for a Large Workload

The following table provides an example of how identity governance activities might occur in a large workload:

Application

Category

Expected Workload

Identity Governance

Identities

Accounts

Groups

Entitlements / permissions

Deltas (per day)

500,000

500,000

7,500

7,500

500,000

Identity Manager

Identities

Events per second

500,000

100

Identity Intelligence (total workload)

Identities

Transactions (per day)

Views (concurrent)

1 million

1 million

10

System Sizing for a Large Workload

Category

Requirement

Cluster node (master+worker)

1

CPU cores (per node)

12

RAM (per node)

64

Disks (per node)

2

Storage per day (1x)

10 GB

Total disk space (365 days)

3 TB

Database Resource Pools Tuning for a Large Workload

Category

Property

Value

Database

active_partitions

tm_concurrency

tm_memory

6

7

6,000

Resource pools

ingest_pool_memory_size

mf_entity_ingest_pool_memory_size

mf_entity_ingest_pool_planned_concurrency

15%

30%

24

Scheduler

plannedconcurrency

tm_memory_usage

maxconcurrency

6

6,000

7

Transformation Hub Tuning for a Large Workload

Property

Quantity

# of Kafka broker nodes in the Kafka cluster

1

# of ZooKeeper nodes in the ZooKeeper cluster

1

# of Partitions assigned to each Kafka Topic

6

# of replicas assigned to each Kafka Topic

1

# of message replicas for the __consumer_offsets Topic

1

Schema Registry nodes in the cluster

1

Kafka nodes required to run Schema Registry

1

# of CEF-to-Avro Stream Processor instances to start

1