MemoryManagementOptions

public struct MemoryManagementOptions

Memory management options.

Note: This is a beta release of this feature, so there could be a few bugs and unexpected behavior. Related APIs may change for new releases without a deprecation process.

memoryManagementStrategy
The default setting MemoryManagementStrategy.DYNAMIC is suitable for common cases. The map data cache can adjust dynamically to fit visible data. When the visible data needs extra memory, it would increase. When it’s not needed, it will reduce to a limit which is calculated internally or by using MapContext.MemoryManagementOptions.tileCacheMemoryLimitInKiB option. The MemoryManagementStrategy.FIXED would be only useful when there is very strict memory consumption requirement for the application. It potentially can have flickering visual artifacts when the map data to be visualized is very large and exceeds the cache limit.
Declaration
Swift

public var memoryManagementStrategy: MapContext.MemoryManagementStrategy
tileCacheMemoryLimitInKiB
Tile cache memory limit in kibibytes. Non positive or nil values are ignored. Default value is nil. Low tile cache limit will lead to eviction of tiles only if MemoryManagementStrategy is set to FIXED.
Declaration
Swift

public var tileCacheMemoryLimitInKiB: Int32?
videoMemoryLimitInKiB
Target video memory limit in kibibytes. Non positive or nil values are ignored. Default value is nil.
Declaration
Swift

public var videoMemoryLimitInKiB: Int32?


                    
                    
                    init(memoryManagementStrategy:tileCacheMemoryLimitInKiB:videoMemoryLimitInKiB:)

Creates a new instance.

Declaration

Swift

public init(memoryManagementStrategy: MapContext.MemoryManagementStrategy = MapContext.MemoryManagementStrategy.dynamic, tileCacheMemoryLimitInKiB: Int32? = nil, videoMemoryLimitInKiB: Int32? = nil)