Table of Contents

Search

  1. Preface
  2. Getting Started with Informatica Address Verification (On-Premises)
  3. General Settings
  4. Input Parameters
  5. Process Parameters
  6. Address Enrichments
  7. Result Parameters
  8. Output Fields
  9. Assessment Codes and Return Codes
  10. Frequently Asked Questions
  11. Geocode Countries

Developer Guide (On-Premises)

Developer Guide (On-Premises)

Memory Management

Memory Management

Informatica Address Verification stores different types of objects, such as address objects, pre-loaded reference address databases, and caches, in its memory. When you make memory allocations for Address Verification, you must consider the different objects that have specific memory requirements.
You can divide the memory requirements of Address Verification into the following blocks:
  • General memory block. Allocated for general management functions. Typically, the general memory block size is 7 MB.
  • Thread memory block. Allocated for address processing and verification routines. Address Verification creates as many thread memory blocks as the number of simultaneous threads you configure it to process.
    The size of a thread memory block is about 38 MB for 32-bit systems and 48 MB for 64-bit systems.
  • Address object memory block. Allocated for storing the address objects defined. Address Verification creates as many address object memory blocks as the number of address objects you configure it to process.
    The size of an address object memory block is about 3.7 MB + (0.24 MB x the value of
    MaxResultCount
    ) in the case of 32-bit systems. For 64-bit systems, the size of an address object memory block is about 4.8 MB + (0.24 MB x the value set for
    MaxResultCount
    ).
  • Memory block reserved for caching. Address Verification reserves one cache memory block for each of the verification or processing threads.
  • Memory blocks for preloading reference address databases. The value for preloading memory block depends on the number and size of the databases that you want to preload.
  • Unallocated memory block.
You can configure the
MaxMemoryUsageMB
parameter to specify the maximum available memory for Address Verification. The values you set for the following parameters control the memory allocation for the memory blocks:
  • MaxThreadCount
    . The maximum number of threads that Address Verification can process simultaneously. The value set for this parameter controls the number of thread memory blocks and the total memory allocation for the thread blocks.
  • MaxAddressObjectCount
    . The maximum number of address objects that Address Verification can store. You can set a value that is two or three times the value you configured for
    MaxThreadCount
    . The value you set for
    MaxAddressObjectCount
    controls the number of address object memory blocks and the total memory allocation for the address objects.
  • CacheSize
    . The memory reserved for caching purposes. If you set
    CacheSize
    to
    None
    , Address Verification does not allocate any memory for caching. If you set
    CacheSize
    to
    Small
    , Address Verification allocates 0.4 MB of cache memory block for each of the threads. If you set
    CacheSize
    to
    Large
    , Address Verification allocates 0.75 MB of cache memory block for each of the threads. For example, if
    MaxThreadCount
    is set to 4 and
    CacheSize
    to
    Small
    , Address Verification allocates 1.6 MB for cache memory block.

0 COMMENTS

We’d like to hear from you!