[
https://issues.apache.org/jira/browse/JENA-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420468#comment-15420468
]
ASF GitHub Bot commented on JENA-1222:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/161
Let's get this into the codebase first (inactive). JENA-1222 and JENA-1224
are both changes to TDB's ``TransactionManager`` and juggling multiple branches
of nearby code changes is not nice.
I've tried to write a test for snapshot isolation promotion but it relies
on a thread pause which elsewhere has been unstable on a heavily loaded CI
server (`TestTransPromote.promote_clash_active_writer`). At the moment, there
is no special code for the "active writer then abort" case. It may be possible
but if it looks like a major change to TDB1, then it may not be worth and may
be a sign that the specific feature is generally something that warps the rest
of the system.
Until we get the contract details settled, changing TIM seems premature.
> Control the flushing of the commit log based on journal size.
> -------------------------------------------------------------
>
> Key: JENA-1222
> URL: https://issues.apache.org/jira/browse/JENA-1222
> Project: Apache Jena
> Issue Type: Improvement
> Components: TDB
> Reporter: Andy Seaborne
>
> See discussion in thread:
> https://lists.apache.org/thread.html/b992db7e843e1444d2c4835ac9ece41bee2b251a60785d8881452b95@%3Cusers.jena.apache.org%3E
> TDB batches commits to save on overheads of small updates. However, if the
> application is continually making large commits then batching saves little,
> and causes more temporary resource consumption (RAM especially). It may also
> cause jitters in performance due to a large updates to the main database.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
