[infinispan-dev] Versioned entries - overview of design, looking for comments

[Manik Surtani]

On 15 Sep 2011, at 14:44, Paolo Romano wrote:

> Concerning costs. For option 2), the prepare message should piggyback 
> the version identifiers of *each* data item that needs to be write-skew 
> checked...which may lead to big messages, if you needed to test a lot of 
> data items. But the ws-check is done only on the data items that are 
> both read and written within the same xact. So I'd expect that normally 
> just a few keys would need to be write-skew checked (at least this would 
> be the case for the wide majority of DBMS/STM benchmarks I've been using 
> so far).  Therefore I would not be too concerned with this issue.

True, but if a vector clock is used as the underlying version scheme, then the updating node would need to send across its local clock for each data item, regardless of whether a ws-check is needed for that data item or not.  Correct?

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20110915/e2e1e831/attachment.html