Kyle Spier-Swenson 5fa115de27 Asset cache updates. (#50759) ...

Asset cache now caches the asset's md5 This should solve the high cpu usage issues with it. line by line profile suggests that the next hotspot is the asset log.

Simplied asset cache code, moved verify functionality to a flush_assets proc that blocks until a client has all currently sending assets. (sidenote: there is an argument for moving most of asset_cache's global procs onto the client, get_asset_datum and register_asset are really the only valid global procs.)

Re-added batched passive sends since it does speed up how quickly the asset cache pre-caches to clients.

2020-05-04 15:08:38 +12:00

..

asset_cache_client.dm

Asset cache updates. (#50759)

2020-05-04 15:08:38 +12:00

asset_cache_item.dm

Asset cache updates. (#50759)

2020-05-04 15:08:38 +12:00

asset_cache.dm

Asset cache updates. (#50759)

2020-05-04 15:08:38 +12:00

asset_list_items.dm

Asset cache updates. (#50759)

2020-05-04 15:08:38 +12:00

asset_list.dm

Asset cache updates. (#50759)

2020-05-04 15:08:38 +12:00

validate_assets.html

…