[
https://issues.jboss.org/browse/ISPN-9932?page=com.atlassian.jira.plugin....
]
Tristan Tarrant updated ISPN-9932:
----------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint
#33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37
(was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33,
DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
Avoid creating MarshallableEntry instances if no CacheWriter enabled
--------------------------------------------------------------------
Key: ISPN-9932
URL:
https://issues.jboss.org/browse/ISPN-9932
Project: Infinispan
Issue Type: Enhancement
Components: Loaders and Stores
Affects Versions: 10.0.0.Alpha3
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Priority: Major
Fix For: 10.0.0.Beta1
The (Dist)CacheWriterIntercepter is enabled if any loader/store is configured. The
problem, is that the interceptor assumes that a CacheWriter is always configured.
However, it is possible that only a CacheLoader has been configured, in which case when a
write command visits the interceptor, MarshallableEntry instances are created
unnecessarily in order to call the various PersistenceManager write operations.
To avoid unnecessary allocations and the marshalling of key/value/metadata that is never
stored, we should ensure that calls to PersistenceManager write methods are only called if
a CacheWriter is actually configured.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)