Gld Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 45: | Line 45: | ||
====reuse-value==== | ====reuse-value==== | ||
By default, the load strategy randomly generates the first entry value and then keeps reusing it, as a speed optimization (reuse-value: "true"). To change this behavior and configure the load strategy to generate a new random value every times it needs one | By default, the load strategy randomly generates the first entry value and then keeps reusing it, as a speed optimization (reuse-value: "true"). To change this behavior and configure the load strategy to generate a new random value every times it needs one, set "reuse-value" to "false". Configuring the load strategy to not reuse values will make it somewhat slower. | ||
Revision as of 20:53, 7 December 2016
Internal
Configuration
-c <cofiguration-file.yml>
If the configuration file is not specified on the command line (where it has priority), it is looked up a value of GLD_CONF_FILE environment variable.
Cache Service Configuration
service:
type: cache
implementation: local
key-size: 10
value-size: 1024
load-strategy:
...
read-then-write-on-miss Load Strategy Configuration
service:
type: cache
...
key-size: 10
value-size: 1024
load-strategy:
name: read-then-write-on-miss
reuse-value: false
reuse-value
By default, the load strategy randomly generates the first entry value and then keeps reusing it, as a speed optimization (reuse-value: "true"). To change this behavior and configure the load strategy to generate a new random value every times it needs one, set "reuse-value" to "false". Configuring the load strategy to not reuse values will make it somewhat slower.