OpenSimulator · EN

Other internal caches: inventory, regions and textures

Practical guide based on OpenSimulator 0.9.3.1 source: identify, configure and diagnose caches.

Check the active module and loaded settings before commands. Caches may be cleared, but permanent stores like FSAssets must never be deleted as if they were caches.

Inventory cache

InventoryCache temporarily stores root folders, system folders and inventory results to avoid repeated remote calls. CACHE_EXPIRATION = 60000 represents about one minute. It is an application memory cache, separate from inventory storage and the viewer cache.

User account cache

Simulator UserAccountCache holds accounts by UUID and name. Source code uses about one hour for ordinary accounts, 48 hours for some foreign accounts and 10 minutes for unsuccessful lookups. Changes may require propagation or invalidation.

Grid region information cache

RegionInfoCache holds region descriptors to reduce Grid service lookups. Typical nonlocal expiration is 120 seconds in this implementation. Moved or renamed regions may appear differently across processes for a short time.

Hypergrid user service cache

The UserAccountCache used by certain Hypergrid services expires after about five minutes. It is not identical to the simulator account cache and has a different expiration and invalidation model.

JPEG2000 texture decoding (J2K)

J2KDecoderModule caches decoded JPEG2000 layer boundaries in memory for around one minute, and can reuse the asset cache interface for stored results. This is not a second authoritative inventory of users' textures.

Avatar bakes and XBakes service

Avatar composite textures (bakes) and optional XBakes services are another appearance-rendering storage/cache mechanism. Distinguish avatar appearance problems, missing assets and slow-loading environmental textures.

Not every cache has a clear command

In the reviewed files, InventoryCache, UserAccountCache and RegionInfoCache are internal structures with expiry/invalidation methods used by application code. This does not establish a console command for clearing them: do not invent commands analogous to fcache.

Managing this cache: practical steps

How to manage these internal caches

Inventory, account and region caches are primarily in memory. Normal management uses automatic expiry and internal invalidation methods. Before restarting a process for stale data, verify that the authoritative service returns the correct value, allow the relevant TTL to pass and inspect logs. Restarting is an operational action with other effects, not a targeted clear command.

J2K and avatar bakes: diagnostics

For J2K issues, first verify the original texture is available, check decoder logs and test the viewer. For avatar appearance problems, distinguish XBakes, appearance records and Firestorm cache. Reviewed source files do not establish one generic console command to clear all of these caches.

Identity cache: dedicated command

The UserManagementModule name cache provides reset user cache, unlike several other internal caches that expire automatically. It does not clear asset caches or ROBUST data. See the account-cache guide for the checks and full procedure.

Full procedure: user cache, checks and commands

More cache guides

Verified sources: OpenSimulator 0.9.3.1