![]() ![]() ![]() Updating your compact cache to leverage performance improvementsīeginning at 10.3, the compact cache storage format was improved to increase performance when consuming cached map and image services. Own logic to pull tiles out of a virtual directory, you shouldĬontinue to use the exploded format, which stores each tile as a single file and was the only option at ArcGIS Server 9.3.1 and previous. The internal architecture of the bundle is not publicly documented by Esri. The server receives the request and returns the appropriate tile from the bundle. In a web situation, the client issues a call to the server for the specific level, row, and column of the tile. Getting tiles from the bundleĪrcGIS clients, including the web APIs, know how to read the bundleįiles produced by the compact cache format. In ArcGIS documentation, this unit of area is sometimes referred to as a supertile. Instead, a finer-grained area of 4096 x 4096 pixels (no antialiasing) or 2048 x 2048 pixels (antialiasing) is updated. When you update tiles in a compact cache, the entire bundle is not re-created. In 10.1 and later releases, the software has more intelligence about how to allocate CPU resources to the cache job, and the geographic size of the feature defining your cache job should not affect CPU utilization. In 10.0 and earlier versions, if you used a feature smaller than a bundle to define the boundaries of your cache job, you could see CPU underutilization. The area of a midsize county in the eastern United States. Neighborhood/street level scale of 1:4096, a full bundle covers about The bundle boundaries are determined by the tiling scheme originĪnd are not adjustable. (although the bundles might not contain the full 16,000 tiles if the geography is small). Portion of the geography, so you get multiple bundles in a level More common is that you have a bundle boundary crossing some It's possible to have a small cache with just one bundle at each done files should go away when the caching job has finished. ![]() done file is the server's way of understanding which bundles have finished. lock file doesn't mean that the bundle is inaccessible to clients. lock files are the server's way of keeping track of which bundles are currently being created the presence of a. While the cache is being created, you may see. You'll also see some corresponding index files with the extension. If you look at a compact cache on disk, you can see the bundle files with the. The result is a cache with dozens or hundreds of files, instead of thousands or millions. The compact cache groups many tiles together in one large fileĬalled a bundle. Scalability is improved when creating tiles with multiple-machine deployments, because of reduced network traffic.Tiles are generally created more quickly because disk I/O is reduced during tile creation.The total size on disk of the cache is reduced.Caches are easier to copy because the number of files is reduced.Advantages of storing tiles in groups include the following: The compact cache storage format allows you to group tiles in large files rather than storing the tiles as individual files. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |