Hi Christian,
On Jul 13, 10:37 am, Christian Vest Hansen
wrote:
> I believe that DeuceSTM i primarily intended as a research platform
> for Java STMs, hence the flexibility with pluggable algorithms.
>
> Another Java STM is multiverse:http://code.google.com/p/multiverse/-
> the focus here is on
> No. I don't want to use transactions for workflow. I don't want
> blocking transactions. I don't want read tracking.
With multiverse it depends on the engine being used and the settings
on the transaction. And readonly transactions also don't track reads.
> > And since Clojure is using MVCC, d
I don't think it every is going to scale.
MVCC/TL2 based STM designs rely on a central clock, so if you can
update the clock in 0.1 ms on all machines, the maximum throughput is
1/0.0001 = 10.000 transactions/second... no matter how many machines
you throw at it. Even on a single machine the centr
wrote:
> > > Hi --
>
> > > I'm noob to both Clojure and Terracotta but if you're willing to
> > > tolerate basic questions from me, I'd be very interested in helping
> > > out.
>
> > > On Jul 12, 3:36 am, peter veentjer wrote:
.g. using agents heavily?
>
> - Chas
>
> On Jul 16, 2010, at 8:00 AM, peter veentjer wrote:
>
> > To repeat myself again:
>
> > The big problem with a MVCC based STM, is that there is a central
> > clock
> > that needs to be touched by independent transactions.
I have got a question about the Clojure ensure and how it actually
works and the documentation doesn't provide enough information.
I see a few different solutions:
1) An optimistic approach: Once a ref is 'ensured' it is included in
the conflict detection set. This means that the approach is stil
t; Stu
>
> > The first one is correct.
>
> > On Tue, Sep 14, 2010 at 3:22 PM, peter veentjer
> > wrote:
> > I have got a question about the Clojure ensure and how it actually
> > works and the documentation doesn't provide enough information.
>
> >
ction object for the current
thread. That acquires a read lock for the Ref which is held until the
transaction commits or until the Ref is set with ref-set or alter
later in the transaction try.
So it looks like it is an encounter time ensure.
On Sep 14, 10:05 pm, peter veentjer wrote:
> Ok,
On Oct 15, 2:51 pm, hobnob wrote:
> Hi,
>
> I'm just starting to get my head wrapped around STM just by reading
> about it so I can make a decision on whether to port a Java project to
> Clojure.
>
> a) can STM transactions contain calculations that take a 'long' time,
> let's say computing the
