urn:infinispan:config:5.2
element storeAsBinary

Super Types

{urn:infinispan:config:5.2} (restriction)

Documentation

            Controls whether when stored in memory, keys and values are stored as references to their original objects, or in a serialized, binary format.  There are benefits to both approaches, but often if used in a clustered mode, storing objects as binary means that the cost of serialization happens early on, and can be amortized.  Further, deserialization costs are incurred lazily which improves throughput. It is possible to control this on a fine-grained basis: you can choose to just store keys or values as binary, or both.
          

Properties

This component is not nillable.

Model

<storeAsBinary
  enabled = xs:boolean
  storeKeysAsBinary = xs:boolean
  storeValuesAsBinary = xs:boolean>

</storeAsBinary>

enabled

Enables storing both keys and values as binary.

Type:

xs:boolean

Use:

optional

Form:

unqualified

storeKeysAsBinary

Specify whether keys are stored as binary or not.

Type:

xs:boolean

Use:

optional

Form:

unqualified

storeValuesAsBinary

Specify whether values are stored as binary or not.

Type:

xs:boolean

Use:

optional

Form:

unqualified

Source

<xs:element minOccurs="0" name="storeAsBinary">
  <xs:complexType>
    <xs:attribute name="enabled" type="xs:boolean">
    </xs:attribute>
    <xs:attribute name="storeKeysAsBinary" type="xs:boolean">
    </xs:attribute>
    <xs:attribute name="storeValuesAsBinary" type="xs:boolean">
    </xs:attribute>
  </xs:complexType>
</xs:element>