Exactly my thoughts.
But in practice if I run a long update (update that causes a large
amount of other updates caused by triggers in the same transaction)
then other queries and updates are blocked when I am using MVCC.
The machine I am using has 4 processors. Only 1 of which is utilized by
the update that is blocking everybody else.
- rami
On 14.6.2010 8:44, James Gregurich wrote:
Why is that? The purpose of MVCC is to allow greater concurrency by giving each
thread an independent view of the db....thus getting rid of row/table
locks....or atleast that is my understanding.
-James
On Jun 13, 2010, at 10:19 PM, Thomas Mueller wrote:
Hi,
Which one of these would be more stable and result in better concurrency?
I'm afraid it's like this: MVCC is more stable, but MULTI_THREADED
provides more concurrency.
Regards,
Thomas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
