Yeah, I've tried a shared cache before and it seems to be okay. It's a bit messy because multiple simulators may
attempt to clean up the cache at the same time, which results in quite a few seeing messy "file not found" warnings,
though these should not be harmful.
It's hard to know how to get around this problem without making the cache yet another process or doing messy things like
designating only one simulator to actually clean up files. I also think the cache needs a facility to limit by size
(like every other cache in the known universe :).
On 22/08/14 15:28, Jeff Kelley wrote:
At 8:09 AM -0500 22/8/14, Marcus Llewellyn wrote:
You can indeed give each instance its own asset cache directory. My rationale
for not doing so is that where simulators
share content, this should reduce requests to the asset service, resulting in
less network traffic, and also a modest
speed up when regions are first started in some circumstances.
Because an asset may have been cached already by another simulator.
My only concern has been that a single asset cache that has multiple copies of
Flotsam managing it might at some point
encounter some sort of conflict or collision. So far, I've noticed nothing of
the sort, though. In practice, a single
asset cache has been working fine for me.
So shared cache is a better option, until we discover a drawback.
-- Jeff
_______________________________________________
Opensim-users mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
--
Justin Clark-Casey (justincc)
OSVW Consulting
http://justincc.org
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
