psa pls don't use transactions for single doc unobserved atomic updates

[Tim Penhey]

There is one that I talked with Kapil about this morning.

When a user connects over the client api, we record the last login time.
Currently this uses a transaction, but doesn't need to.  In fact using a
transaction here takes an order of magnitude longer, and wakes up
watchers when it doesn't need to (because of a new transaction).

This is certainly something that is worthwhile looking at, and
determining a pattern for.

Tim

On 22/09/14 10:54, David Cheney wrote:
> Hi Kapil,
> 
> I'm sure that the 'put everything in a transaction' pattern is applied
> unilaterally.
> 
> Do you have some specific operations in mind ?
> 
> Dave
> 
> On Mon, Sep 22, 2014 at 7:46 AM, Kapil Thangavelu
> <kapil.thangavelu at canonical.com> wrote:
>> Its sort of misses the point on why we're doing client side transactions.
>> Mongodb has builtin atomic operations on an individual document. We use
>> client side txns (multiple order of magnitude slower) for multi-document
>> txns *and/or* things we want to observe for watches.
>>
>> -k
>>
>>
>> --
>> Juju-dev mailing list
>> Juju-dev at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>