[
https://issues.apache.org/jira/browse/OPENJPA-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18128501#comment-18128501
]
ASF subversion and git services commented on OPENJPA-2950:
----------------------------------------------------------
Commit a525594b01ed2e1d7075464beea2b1859dcbe95d in openjpa's branch
refs/heads/OPENJPA-2951 from Paulo Cristovão de Araújo Silva Filho
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=a525594b0 ]
Merge pull request #215 from apache/OPENJPA-2950
[OPENJPA-2950] Flush before a query for the access path, not for the whole
context
> Broadened auto-flush before every query hurts perf
> --------------------------------------------------
>
> Key: OPENJPA-2950
> URL: https://issues.apache.org/jira/browse/OPENJPA-2950
> Project: OpenJPA
> Issue Type: Sub-task
> Components: jpa
> Affects Versions: 4.2.0
> Reporter: Maxim Solodovnik
> Priority: Major
> Fix For: 4.2.0
>
>
> Discussion link:
> https://github.com/apache/openjpa/pull/144#discussion_r3682999345
> **(medium)** With FLUSH_TRUE (default FlushModeType.AUTO) this now flushes
> before every query as soon as anything in the context is dirty, and the
> `flush == FLUSH_TRUE` addition at line 1033 also overrides the IgnoreChanges
> setting. That defeats the access-path optimization and can be a real perf
> regression in write-heavy transactions - can the broadened check be limited
> to types related to the query access path, or guarded by a compatibility flag?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
