[Opensim-dev] Proposal: Implement a de-duplicating core ROBUST asset service
Mike Chase
mike.chase at alternatemetaverse.com
Fri Mar 9 15:53:57 UTC 2012
On Fri, 2012-03-09 at 16:47 +0100, Bo wrote:
> Hello,
> allow me a few noob comments, please :
>
> 1) worst thing you can have in a big table is a VERY variable row length.
> 2) systems like http://en.wikipedia.org/wiki/Google_File_System have very good
> performance and are perfectly scalable
> 3) you can have floatsam cache also on multiple disks (eg assets with
> checksums starting at a-g) on one disk and so long
> 4) it is easy to BACKUP such a storage. For example you can use rsyncand
> download only the new assets
> 5) it is easy to develop custom scalable solutions
> etc etc...
>
> Have assets in the MySql is a fine solution for standalones and very small
> grids. Please, don't change it, if you feel this as the only OS future..
Yeah... If the focus of the core code out of the box is small sims and
standalones as Justin implied then even doing de-dup sounds like rather
a waste of time. Better to validate the interface can handle a real
commercial grade asset server using something like NoSQL. De-dup sounds
risky at best and probably not worth the cycles if your going to scale
and probably need to replicate data in a clustered configuration anyway.
Honestly there are other fish to fry as the saying goes. I'd leave this
one alone.
Mike
> Bo
>
> On Friday 09 of March 2012 16:36:50 M.E. Verhagen wrote:
> > 2012/3/9 Wade Schuette <wade.schuette at gmail.com>
>
> > And as the opensim worlds are user generated worlds, lots of people do not
> > really care about things like small textures or small meshes.
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
More information about the Opensim-dev
mailing list