As I think Mic has proposed before, I believe it's possible to clean up assets in a distributed grid if you track access times.

Essentially, periodically when as asset is fetched from the asset service (e.g. every 6 months), the access time is updated. Then you reap assets which have an access time older than 3 years, for instance.

Off the top of my head, this would rely on the following conditions:

1) Regions periodically clear their asset caches and preferably fetch all assets referenced in the scene. This periodic fetch is somewhat like taking an OAR, which should also fetch all assets in the scene. An alternative to fetch would be a more inexpensive asset ping. If regions cache indefinitely then asset access times may go stale. Of course, this reduces cache efficiency.

2) One periodically sweeps through each users inventory and pings/fetches associated assets. This is what fetching an IAR effectively does. This could be done over a fairly long period without disrupting grid operations.

There is always going to be some risk in asset removal but I think that it 
would be negligible if these conditions were met.

Unfortunately, the existing asset database plugins, at least the MySQL time, have an access_time field but for some reason never updates it, making it completely useless. The deduplicating XAssetService does implement this and works perfectly (I've been using it for more than a year now) but I haven't yet fully thought out the process for finally migrating from the existing asset service. Of course, deduplicating also significantly reduces asset db bloat.

On 30/03/14 13:48, Fleep Tuque wrote:
That sounds terrifying.  Has anyone actually done this on a large or old grid 
successfully?

- Fleep

On Sun, Mar 30, 2014 at 4:50 AM, M.E. Verhagen <[email protected] 
<mailto:[email protected]>> wrote:

    the only way to clean up the database is to do a rebuild. Save everything 
in iar and oar files and restore them in a
    new database.

    Or buy yourself a 3tb harddisk

    _______________________________________________
    Opensim-users mailing list
    [email protected] <mailto:[email protected]>
    https://lists.berlios.de/mailman/listinfo/opensim-users




_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users



--
Justin Clark-Casey (justincc)
OSVW Consulting
http://justincc.org
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users

Reply via email to