Are there any restrictions on data volume related to capability, performance etc. in Semarchy xDM?
Best Answer
C
Cédric BLANC
said
over 2 years ago
Scaling of an xDM application depends on how the data hub is accessed and used.
Scaling the application server nodes: If the number of simultaneous users and applications accessing the MDM grows (Web Services, UI Screens, etc.) then the bottleneck tends to be at the application server level. In that case, you can either add additional app server nodes to your cluster or augment both the CPU and RAM on each of the nodes.
Scaling the relational database: If the volume of data grows then the bottleneck tends to be the database engine. The default standard recommendation is 4 cores every 1-3 million records. All database technologies used (Oracle, PostgreSQL, or Microsoft SQL Server) scale extremely well.
1 Comment
Cédric BLANC
said
over 2 years ago
Answer
Scaling of an xDM application depends on how the data hub is accessed and used.
Scaling the application server nodes: If the number of simultaneous users and applications accessing the MDM grows (Web Services, UI Screens, etc.) then the bottleneck tends to be at the application server level. In that case, you can either add additional app server nodes to your cluster or augment both the CPU and RAM on each of the nodes.
Scaling the relational database: If the volume of data grows then the bottleneck tends to be the database engine. The default standard recommendation is 4 cores every 1-3 million records. All database technologies used (Oracle, PostgreSQL, or Microsoft SQL Server) scale extremely well.
Cédric BLANC
Are there any restrictions on data volume related to capability, performance etc. in Semarchy xDM?
Scaling of an xDM application depends on how the data hub is accessed and used.
Scaling the application server nodes: If the number of simultaneous users and applications accessing the MDM grows (Web Services, UI Screens, etc.) then the bottleneck tends to be at the application server level. In that case, you can either add additional app server nodes to your cluster or augment both the CPU and RAM on each of the nodes.
Scaling the relational database: If the volume of data grows then the bottleneck tends to be the database engine. The default standard recommendation is 4 cores every 1-3 million records. All database technologies used (Oracle, PostgreSQL, or Microsoft SQL Server) scale extremely well.
Cédric BLANC
Scaling of an xDM application depends on how the data hub is accessed and used.
Scaling the application server nodes: If the number of simultaneous users and applications accessing the MDM grows (Web Services, UI Screens, etc.) then the bottleneck tends to be at the application server level. In that case, you can either add additional app server nodes to your cluster or augment both the CPU and RAM on each of the nodes.
Scaling the relational database: If the volume of data grows then the bottleneck tends to be the database engine. The default standard recommendation is 4 cores every 1-3 million records. All database technologies used (Oracle, PostgreSQL, or Microsoft SQL Server) scale extremely well.
-
Can we reset Matches and run again on match rule change or add a new match rule?
-
"Unmerge" records
-
Turn off match rules to speed up an integration job
-
Can anyone tell me how to load a Fuzzy-Matched entity ... but skip the matching happening auto-magically?
-
Importing CSV in Fuzzy Matched Entity Does Not Trigger Consolidation
-
How can I trigger a "match on child records"?
-
How can I Configure Most Frequent Values in Survivorship Rules?
-
Deterministic or probabilistic matching
-
Machine Learning and AI for matching
-
Prevent loads from replacing values overridden by users
See all 45 topics