6.1
How to I set up cache and thread settings in e2 Vault? Are there any best practices? I am using e2routerd with three rendering engines.
For e2renderd/e2serverd/e2routerd I prefer to enable cache and thread pool debug messages:
For e2renderd/e2serverd/e2routerd I prefer to enable cache and thread pool debug messages:
[pool1]
debug=1
[cache1]
debug=1
You can optionally turn on the debug logging for the stat component but I don't usually use it.
[stat1]
debug=1
Specifically for e2routerd I also enable debug messages for the router component:
[router1]
debug=1
For [server1] service= I usually use * for the address so it binds to all interfaces. There are cases where you might want to specify the interface but that is less common.
[server1]
service=*:7004
UPDATED:
October 18, 2017