Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
2.0.0, 2.0.1, 2.1.1, 2.2.0
-
None
-
None
Description
I'm proposing that we change the default behavior for the DataCache. Currently, the DataCache is turned off by default. Our competition is turning on their L2 cache by default. Thus, out-of-the-box comparisons are killing us. We have to explain the difference, get them to change the configuration one way or the other for apples-to-apples comparisons, and then re-run the benchmark. By that time, it's too late. We already lost.
Due to the upcoming 2.0.0 release, it seems like a good time to change this default. Please comment directly to this JIRA.
Thanks,
Kevin
Attachments
Issue Links
- is blocked by
-
OPENJPA-1767 OneToMany relationships owned by the many side aren't properly evicted from the DataCache
- Open
-
OPENJPA-1768 StackOverflowError when finding an Entity with an Eager ManyToMany relationship.
- Closed
-
OPENJPA-1770 Inconsistent behaviour when fetching an Entity that has a null embeddable and the DataCache is enabled
- Closed
- is related to
-
OPENJPA-1443 Turn on some additional DataCache and PCData testcases
- Closed
1.
|
Change the default QueryCache eviction policy. | Closed | Unassigned | |
2.
|
Turn off QueryCache by default | Closed | Kevin W. Sutter |