Gld Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
implementation: local | implementation: local | ||
key-size: 10 | key-size: 10 # optional, if not specified, the default value is 12 characters | ||
value-size: 1024 | value-size: 1024 # optional, if not specified, the default value is 512 characters | ||
load-strategy: | load-strategy: | ||
| Line 43: | Line 43: | ||
type: cache | type: cache | ||
... | ... | ||
load-strategy: | load-strategy: | ||
Revision as of 22:51, 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.
Load Configuration
service: ... load: threads: 10 requests|operations|messages: 1000 # optional, if not specified load will be generated forever
Cache Service Configuration
service:
type: cache
implementation: local
key-size: 10 # optional, if not specified, the default value is 12 characters
value-size: 1024 # optional, if not specified, the default value is 512 characters
load-strategy:
...
read-then-write-on-miss Load Strategy Configuration
service:
type: cache
...
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.