On Jan 7, 2018, at 2:20 AM, Brendan Duddridge <[email protected]<mailto:[email protected]>> wrote:
I see it says Level 2 though, so does that mean that the main transaction (Level 1) was created by the inTransaction call and these are just sub-transactions of that one transaction? They’re just sub-transactions. Not even that really; they just bump a transaction-level counter. We only commit the SQLite transaction when the counter decrements to zero. Is there a way to prevent the sub-transactions from being created and committed for every purgeDocument call? It's operating quite slowly with all these transactions. They shouldn’t affect performance, because all they do is alter an internal counter. Try profiling with Instruments to see where the time is going. It may be something else about the purge process that’s slow. —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/4EC82B75-466E-48D0-9AE4-ACE705E04D3B%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
