Determines whether the namespace for UDAs is preloaded at application startup.
PRELOADUDANAMESPACE appname TRUE | FALSEappname—Application for which the UDA namespace is preloaded at start up.
TRUE—Namespace for UDAs is preloaded at application startup.
FALSE—The default. Namespace for UDAs is paged into memory, as needed.
Because querying member sets by UDA can take a long time in large outlines (for example, with one million or more members), in which many members (for example, half a million members) are assigned to one UDA, and login time can be slow for users with filters containing UDAs, preloading the UDA namespace may improve performance. However, preloading the UDA namespace uses additional memory. To calculate the additional memory consumption, use these formulas:
32-bit platforms:
Four additional bytes are used per UDA associated with a member, plus 12 bytes per distinct UDA. The formula:
(#_of_members x #_of_UDAs_per_member x 4 bytes) + (#_of_distinct_UDAs x 12 bytes)
64-bit platforms:
Eight additional bytes are used per UDA associated with a member, plus 24 bytes per distinct UDA. The formula:
(#_of_members x #_of_UDAs_per_member x 8 bytes) + (#_of_distinct_UDAs x 24 bytes)
For example, for an outline with 1,000,000 members and 500,000 distinct UDAs, in which two UDAs are associated with each member, the additional memory needed is:
32-bit platforms:
(1,000,000 members x 2 UDAs associated to each member x 4 bytes) + (500,000 distinct UDAs x 12 bytes) ≈ 14 MB
64-bit platforms:
(1,000,000 members x 2 UDAs associated to each member x 8 bytes) + (500,000 distinct UDAs x 24 bytes) ≈ 28 MB
PRELOADUDANAMESPACE ASOsamp TRUE