Hi Bart,
Virtuoso uses read committed isolation level by default, such that no read will
block waiting for a lock held by another client, see:
http://docs.openlinksw.com/virtuoso/virtuosofaq.html#virtuosofaq30
Locks can be monitored using the Virtuoso sys_l_stat view as detailed at:
Hello list,
A student of mine is doing a performance test with Virtuoso, and he
asked me to pose the following question to this mailing list:
"How are row and page level locks handled when querying the triplestore
(only read stuff with SPARQL, no data inserts or SPARUL)? Is it
possible to get
