[infinispan-dev] Tree API module wiki

[Eduardo Martins]

You mean we will get 5-10% if implementing the parent, child relations
ourselves, where needed? That would for sure be worth the data model
rework. The child relation would be done using a cache map entry with
a set/array value? If yes wouldn't that lock the parent on each child
insert/removal?

-- Eduardo
..............................................
http://emmartins.blogspot.com
http://redhat.com/solutions/telco


On Fri, Nov 26, 2010 at 1:05 PM, Manik Surtani <manik at jboss.org> wrote:
>
> On 25 Nov 2010, at 03:24, Eduardo Martins wrote:
>
>> Great, finally an easy migration from JBoss Cache.
>>
>> Just to know our options in Mobicents future, are there any cons on
>> using this API? Is there a reason to change a data model/schema coming
>> from JBoss Cache, that really takes advantage of node relations
>> parent/child? For instance it's very common to retrieve the set of
>> childs for a node, another common usage is the removal for a complete
>> subtree. We have time to rework this data model if it's not the best
>> usage, we want it as fast as possible, both local and cluster/cloud
>> modes.
>
> There is nothing wrong with using the Tree API, except that it doesn't perform as well as the flat API.  Now don't let this scare you off - in terms of performance, we're talking 5 ~ 10% and if the API works better for you, then use it.  But you should benchmark for yourself and see whether you need to extract this extra performance in exchange for reworking your data model.  YMMV.  :-)
>
> Cheers
> Manik
>
> --
> Manik Surtani
> manik at jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
>
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>