On 17/01/12 22:14, Simon Helsen wrote:
4) I understand what you're new strategy is, but could this not lead to
starvation of read transactions?
No - a reader can't be overtaken by a later writer so no starvation. A
reader sees the state of the database as at the last committed write
transaction, and does not see any changes from any later writers (the
isolation level is "serialized" even through there is concurrency).
Readers are not blocked by writers, unlike TDB upto 0.8.x.
Can you provide us with something to run the tests ourselves? You have
said in the past its part of a larger test framework but if it can't be
separated out doesn't that indicate the rest of the test framework is
caught up in the numbers?
Maybe an addition to the emerging performance framework JenaPerf [1]?
(It's in scala but, writing "better Java" is a good way to start scala)
https://svn.apache.org/repos/asf/incubator/jena/Experimental/JenaPerf/trunk/
Andy
