TileLoadingPolicy Enumeration
Specifies the manner in which a TileLayer, GlobeTileLayer or GlobeView loads tiles.
NuGet/Assembly: Carmenta.Engine.5.16.2.nupkg (in the CECore assembly)
Syntax
public enum TileLoadingPolicyValues
| Value name | Value | Description |
|---|---|---|
| Parallel | 0 | The view area is divided into smaller tiles which are loaded by a task based scheduler. The task based scheduler determines at runtime, depending on the actual CPU the application is running on, how many background threads are used. |
| OneByOne | 1 | The view area is divided into smaller tiles which are loaded one by one on a background thread. This policy corresponds to how Carmenta Engine behaves in version 5.8 and earlier. |
Remarks
The Parallel is the recommended policy since it allows the performance of a configuration to automatically scale with the hardware it is running on.
The task based scheduler is shared by all objects using the parallel tile loading policy in a Carmenta Engine process, which means that the order in which tiles are loaded is undefined. Another side effect of the parallel tile loading policy is that peak memory usage while tiles are being loaded can be higher than before because more work is being done simultaneously.
Limitations
The parallel tile loading policy is not supported for configurations that make use of custom operators, unless those have been coded to handle parallel requests and marked as such with the CustomOperatorProxy.IsThreadSafe property.
Parallel tile loading is also disabled if less than two cores are available to the process.
If Carmenta Engine determines that the parallel tile loading policy is not supported, it automatically falls back to load tiles one by one.
Platforms
Windows, Linux, Android