Installation and Getting Started Guide

6.4.0
- 6.3.0
- 6.2.0
- 6.1.0
- 6.0.0

Back Next

Memory Requirements

Informatica Address Verification stores different types of objects, such as address objects, pre-loaded reference address databases, and caches, in memory. When you define memory allocations for Address Verification, consider the different objects and their combined memory requirements.

The IDVEConfig.json file stores the properties that define the memory requirements. Update the property values if necessary to suit your installation.

Consider the following values when you review the memory requirements:

MaxMemoryMegabytes. The total amount of memory that the data verification engine may allocate for data preloading and processing.

NumFunctionServers. The number of function servers available for processing. Also, determines the number of inputs that the engine can process in parallel.

NumHotStandbyFunctionServers. The number of standby function servers.

FileSetsHotSwappingEnabled. Enables or disables dynamic switches between two file sets.

MaxNumJobs. The maximum number of jobs that can exist concurrently.

MaxNumInputs. The maximum number of addresses that you can submit for verification in a single job.

MaxNumResults. The maximum number of address results that the function can return after execution.

MaxNumVariants. The maximum number of output variants that the function can return after execution.

NumLargeInternalOutputBuffers. The number of large output buffers that the engine creates during initialization. The buffers contribute to the required memory when you use the Java or Microsoft .NET wrapper that Informatica provides for the engine.

The default value on the MaxMemoryMegabytes property is 1024 MB. The default configuration values are sufficient to initialize the engine, but they are not likely to be adequate for data preloading.

The Java and .NET APIs are wrappers for the C API.

Engine execution takes place outside Java in unmanaged code.

Calculating Memory Requirements

You can use the following formula to calculate the amount of shared memory that the engine will try to allocate during initialization:

34 MB + (MaxNumJobs * Job Size in MB) + (Total Function Server Count * 35 MB)

The formula contains the following elements:

34 MB and 35 MB. Constant values that represent internal engine activity.

MaxNumJobs. The maximum number of jobs that can exist concurrently, as represented by the MaxNumJobs property.

Total Function Server Count. The sum of the NumFunctionServers and NumHotStandbyFunctionServers property values. If you enable file set hot-swapping, double the values.

Job Size. The job size recorded in the initialization log. The following string shows a sample log entry:

[IDVE] STATUS: Creating AV jobs in shared memory (16 jobs at 54608085 B each)

In this string, 54608085 bytes represents the job size.

Sample Scenarios

The following table describes a range of installation scenarios and the approximate quantities of memory that each may require:

	Batch, single input, medium volumes (10M+)	Batch, single input, large volumes (100M+)	Batch, bulk input, large volumes (100M+)	QuickCapture / Interactive, large volumes (100M+)	Enterprise service provider, extra large volumes (500M+)
NumFunctionServers	4	8	8	8	16
NumHotStandby FunctionServers	1	1	1	1	4
FileSetsHotSwapping Enabled	false	false	false	false	true
MaxNumJobs	4	8	8	8	16
MaxNumInputs	1	1	1000	1	100
MaxNumResults	1	1	1	100	100
MaxNumVariants	1	3	3	3	3
Minimum required memory (approximate)	2,592 MB	4,612 MB	8,772 MB	4,967 MB	20,975 MB
Shared memory portion (approximate)	211 MB	355 MB	4,503 MB	708 MB	2,268 MB

The minimum required memory value in each scenarios does not include memory for data preloading.

Rename Saved Search

Table of Contents

Installation and Getting Started Guide

Installation and Getting Started Guide

Memory Requirements

Memory Requirements

Calculating Memory Requirements

Sample Scenarios