MaterialsImplDiscussion
From OpenSimulator
(Difference between revisions)
(Created page with "= Introdution = justincc's notes on alternative possibility for materials implementation = Background = Materials are serialized OSD. = Approaches = ==Purely in memory cac...") |
|||
| Line 8: | Line 8: | ||
= Approaches = | = Approaches = | ||
| − | == | + | ==Store materials data in memory cache until persistence definitely required== |
Materials are kept in a purely in memory cache and only added to the asset service when required due to | Materials are kept in a purely in memory cache and only added to the asset service when required due to | ||
Revision as of 10:55, 4 July 2014
Contents |
Introdution
justincc's notes on alternative possibility for materials implementation
Background
Materials are serialized OSD.
Approaches
Store materials data in memory cache until persistence definitely required
Materials are kept in a purely in memory cache and only added to the asset service when required due to
- region cross
- teleport (if on attachments)
- IAR saving
- OAR saving
- simulator shutdown
Cons
- Cache needs to be managed (chiefly removal of items when no longer required).
Pros
- Materials can be rapidly changed without [de]serialization or asset storage overhead.
