GsSetFileMemoryLimit - geostan_1 - 2024.01

GeoStan Geocoding Suite Reference for Windows, Linux, and z/OS

Product type
Software
Portfolio
Locate
Product family
GeoStan Geocoding Suite
Product
GeoStan Geocoding Suite > GeoStan
Version
2024.01
Language
English
Product name
GeoStan
Title
GeoStan Geocoding Suite Reference for Windows, Linux, and z/OS
Copyright
2024
First publish date
1994
Last updated
2024-07-29
Published on
2024-07-29T23:01:18.924000

Deprecated. Controls the amount of memory used for memory mapped files.

Syntax

int GsSetFileMemoryLimit (intlu megabytes)

Arguments

megabytes   Amount of memory to budget for memory mapped files. 0-4294 megabytes. If you input 0, GeoStan uses a small cache and reads from the disk. If you use the maximum amount, GeoStan maps as many files as possible until the limit is exhausted. Input.

Return Values

GS_SUCCESS   

GS_ERROR   You must call GsSetFileMemoryLimit before calling GsInit_r.

Prerequisites

None

Notes

GsSetFileMemoryLimit helps you control the amount of memory GeoStan uses by providing you with a way to set the memory limit for mapped files. Mapped files are the gsd, gsu, gsi, cbsac.dir, finmbr.dat, and us.gsl files.

Call GsSetFileMemoryLimit before GsInit_r. GsSetFileMemoryLimit returns a warning if called more than once per process.

If you are using DPV and LACSLink, you must call GsInitDpv_r and GsInitLACSLink_r after GsSetFileMemoryLimit and before GsInit_r. Although the DPV and LACSLink files are not memory mapped files, these libraries load large files that can cause GsInit_r to fail if not enough memory is reserved.

To determine the amount of virtual bytes used by your process, set the file limit to 0 and run your process.