Understanding OpenSimulator caches
Practical guide based on OpenSimulator 0.9.3.1 source: identify, configure and diagnose caches.
What is a cache?
A cache temporarily keeps data already fetched or computed to reduce database, network, disk or CPU work. Do not confuse it with permanent storage: missing cache entries may be re-fetched from their authoritative service.
Cache layers are independent
Firestorm has its own PC-side cache. A simulator can cache assets on disk via Flotsam and hold other data in memory. ROBUST may use FSAssets or a persistent asset database. Inventory, region, user and J2K caches live elsewhere in the code. Clearing Flotsam does not clear Firestorm or MySQL caches.
Cache, persistent storage and backup
A simulator's assetcache folder stores temporary copies of assets requested by the simulator. A grid's fsassets directory contains persistent asset data. Never confuse these paths. Deleting FSAssets as if it were a cache can cause real content loss. Neither a cache nor a purge is a backup.
Why caches grow
Regions, textures, meshes, scripts, outfits and Hypergrid travel increase asset requests. Disk caches can accumulate large numbers of small files, consuming space and inodes. A large cache can nevertheless be healthy.
Why not purge everything routinely
Removing cached copies forces the simulator to reload assets from remote or persistent services. This increases network, CPU, I/O and loading work temporarily. Reserve purges for diagnosed issues, planned maintenance or verified bad data.
Which symptoms suggest which cache?
An asset reported missing then created: inspect negative caching. A disk cache consuming inodes: inspect Flotsam expiration. Stale inventory or user data: consider application caches and service availability. Low FPS for only one person: start with their viewer and GPU, not ROBUST.
Simplified diagram: these layers are separate. FSAssets is persistent storage, not a disposable cache.
VIEWER FIRESTORM (PC) : textures / meshes / cache d'inventaire SIMULATEUR : Flotsam assets disque + mémoire + négatif SIMULATEUR : caches en RAM (régions / utilisateurs / inventaire / J2K) ROBUST / SERVICE : base d'assets / FSAssets / métadonnées SQL LINUX / MYSQL : caches du système d'exploitation et du moteur SQL
Managing this cache: practical steps
Management approach by cache type
Use [AssetCache] and fcache for Flotsam. Configure ubOde physical mesh caching with [Mesh] and its MeshCache files. Account, region and inventory caches expire or are invalidated through application code, with no verified universal clear command. YEngine folders may contain script state and must not be treated as disposable caches.
Before any cleanup
Record the process name, active module, effective INI setting, file path, disk usage and symptoms. Prefer read-only diagnostics; never delete fsassets, a SQL database or ScriptEngines thinking it is an ordinary cache.
Choose the right guide
For concepts, read Flotsam or internal caches. For console commands, use the fcache or account-cache guide. For an incident, start with cache troubleshooting. Each detailed guide distinguishes local operations from grid-wide changes.
- Flotsam: disk, memory and negative caches
- Cache console commands: fcache
- User caches: reset user cache and diagnostics
- Other internal caches: inventory, regions and textures
- Troubleshoot caches without disrupting a grid
- FSAssets and asset storage
- Inodes and disk storage
- Firestorm cache and graphics lag