Maxim Solodovnik created OPENJPA-2950:
-----------------------------------------
Summary: 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
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)
