MatchUp Hub:Establishing Benchmarks - Revision history

Admin at 18:54, 1 October 2018

2018-10-01T18:54:21Z

← Older revision		Revision as of 18:54, 1 October 2018
Line 10:		Line 10:
	The benchmark should be established running the sample data local with respect to the local installation, use the recommended default matchcode, and should not use available advanced options.		The benchmark should be established running the sample data local with respect to the local installation, use the recommended default matchcode, and should not use available advanced options.

	*[ftp://ftp.melissadata.com/SampleCodes/Current/MatchUp/mdBenchmarkData.~~txt~~ MatchUp Benchmark Data]		*[ftp://ftp.melissadata.com/SampleCodes/Current/MatchUp/mdBenchmarkData.zip MatchUp Benchmark Data]

	For MatchUp Object, we have provided [[MatchUp Hub:Library#Benchmarking\|sample benchmarking scripts]]. For ETL solutions, benchmarks should use the following configured settings, which simulate the most basic usage of the underlying object. And also represents the first step in a Proof of Concept to Production migration….		For MatchUp Object, we have provided [[MatchUp Hub:Library#Benchmarking\|sample benchmarking scripts]]. For ETL solutions, benchmarks should use the following configured settings, which simulate the most basic usage of the underlying object. And also represents the first step in a Proof of Concept to Production migration….

Admin at 18:59, 25 September 2018

2018-09-25T18:59:09Z

← Older revision		Revision as of 18:59, 25 September 2018
Line 12:		Line 12:
	*[ftp://ftp.melissadata.com/SampleCodes/Current/MatchUp/mdBenchmarkData.txt MatchUp Benchmark Data]		*[ftp://ftp.melissadata.com/SampleCodes/Current/MatchUp/mdBenchmarkData.txt MatchUp Benchmark Data]

	For MatchUp Object, we have provided sample benchmarking scripts. For ETL solutions, benchmarks should use the following configured settings, which simulate the most basic usage of the underlying object. And also represents the first step in a Proof of Concept to Production migration….		For MatchUp Object, we have provided [[MatchUp Hub:Library#Benchmarking\|sample benchmarking scripts]]. For ETL solutions, benchmarks should use the following configured settings, which simulate the most basic usage of the underlying object. And also represents the first step in a Proof of Concept to Production migration….

	[[File:MCO_Benchmark_ChartStep2.png\|link=]]		[[File:MCO_Benchmark_ChartStep2.png\|link=]]

Admin at 23:39, 24 September 2018

2018-09-24T23:39:32Z

← Older revision		Revision as of 23:39, 24 September 2018
Line 10:		Line 10:
	The benchmark should be established running the sample data local with respect to the local installation, use the recommended default matchcode, and should not use available advanced options.		The benchmark should be established running the sample data local with respect to the local installation, use the recommended default matchcode, and should not use available advanced options.

	~~===Get Benchmarking Files===~~		*[ftp://ftp.melissadata.com/SampleCodes/Current/MatchUp/mdBenchmarkData.txt MatchUp Benchmark Data]

	For MatchUp Object, we have provided sample benchmarking scripts. For ETL solutions, benchmarks should use the following configured settings, which simulate the most basic usage of the underlying object. And also represents the first step in a Proof of Concept to Production migration….		For MatchUp Object, we have provided sample benchmarking scripts. For ETL solutions, benchmarks should use the following configured settings, which simulate the most basic usage of the underlying object. And also represents the first step in a Proof of Concept to Production migration….

Line 45:		Line 46:

	If returned benchmark results do not closely resemble the expected benchmarks provided by Melissa Data, please fill and return the Benchmark form and return to Melissa Data. Completeness and additional comments provided can help eliminate current or potential performance issues when the process is scaled up to resemble a production process.		If returned benchmark results do not closely resemble the expected benchmarks provided by Melissa Data, please fill and return the Benchmark form and return to Melissa Data. Completeness and additional comments provided can help eliminate current or potential performance issues when the process is scaled up to resemble a production process.

			*[ftp://ftp.melissadata.com/SampleCodes/Current/MatchUp/MatchUpBenchmarkForm.dotx MatchUp Benchmark Form]


	[[Category:MatchUp Hub]]		[[Category:MatchUp Hub]]

Admin: Created page with "← MatchUp Hub ==Migrating from Proof of Concept to Production Deployment== The purpose of the establishing a benchmark – before proceeding to live prod..."

2018-09-24T23:36:14Z

Created page with "← MatchUp Hub ==Migrating from Proof of Concept to Production Deployment== The purpose of the establishing a benchmark – before proceeding to live prod..."

New page

[[MatchUp Hub|← MatchUp Hub]]

==Migrating from Proof of Concept to Production Deployment==
The purpose of the establishing a benchmark – before proceeding to live production data and custom matchcodes is to establish that the said requirements will be possible in your environmment.

[[File:MCO_Benchmark_ChartStep1.png|link=]]

For this reason, we have provided a 1 million record benchmarking file to establish that your environment will most likely not cause slow performance when moving forward. In each benchmarking case.

The benchmark should be established running the sample data local with respect to the local installation, use the recommended default matchcode, and should not use available advanced options.

===Get Benchmarking Files===
For MatchUp Object, we have provided sample benchmarking scripts. For ETL solutions, benchmarks should use the following configured settings, which simulate the most basic usage of the underlying object. And also represents the first step in a Proof of Concept to Production migration….

[[File:MCO_Benchmark_ChartStep2.png|link=]]

A simple file read, MatchUp keybuilding, deduping and output result stream will be established as the lone Data Flow operation…

[[File:MCO_Benchmark_DataFlow.png|link=]]

All distributions of MatchUp provide the benchmark matchcode…

[[File:MCO_Benchmark_Matchcode.png|link=]]

Basic input Field Mapping should be checked…

[[File:MCO_Benchmark_FieldMapping.png|link=]]

Force generation of important output properties compiled during a MatchUp process, although we’ll evaluate only the Result Code property to get Total record and Duplicate counts…

[[File:MCO_Benchmark_Options.png|link=]]

Although configuring Pass-Through options for all source data fields should have a negligible effect on our benchmarking, it should be noted that in actual production, Passing a large amount of source data and or Advanced Survivorship can slow down a process considerably….

[[File:MCO_Benchmark_PassThrough.png|link=]]

We’ll create two output streams that will allow us to tally the Total and Duplicate counts….

[[File:MCO_Benchmark_Output.png|link=]]

After the benchmark program has been configured and successfully run, you are ready to make small incremental steps…

[[File:MCO_Benchmark_ChartStep3.png|link=]]

If returned benchmark results do not closely resemble the expected benchmarks provided by Melissa Data, please fill and return the Benchmark form and return to Melissa Data. Completeness and additional comments provided can help eliminate current or potential performance issues when the process is scaled up to resemble a production process.

[[Category:MatchUp Hub]]