status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Tweaks wording in performance guide.

This commit is contained in:
James Phillips 2016-08-24 22:10:59 -07:00
parent 57db4bcce6
commit c432aa540d
No known key found for this signature in database
GPG Key ID: 77183E682AC5FC11
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
website/source/docs/guides/performance.html.markdown
View File

@ -66,13 +66,13 @@ Here are some general recommendations:
another fast disk technology for the best write throughput. another fast disk technology for the best write throughput.
* <a name="last-contact"></a>Spurious leader elections can be caused by networking issues between * <a name="last-contact"></a>Spurious leader elections can be caused by networking issues between
the servers or lack of CPU. Users in cloud environments often bump their servers up to the next the servers or insufficient CPU resources. Users in cloud environments often bump their servers
instance class with improved networking and CPU until leader elections stabilize, and in Consul up to the next instance class with improved networking and CPU until leader elections stabilize,
0.7 or later the [performance parameters](/docs/agent/options.html#performance) configuration and in Consul 0.7 or later the [performance parameters](/docs/agent/options.html#performance)
now gives you the option to trade off performance instead of upsizing servers. You can use the configuration now gives you tools to trade off performance instead of upsizing servers. You can
[`consul.raft.leader.lastContact` telemetry](/docs/agent/telemetry.html#last-contact) to help use the [`consul.raft.leader.lastContact` telemetry](/docs/agent/telemetry.html#last-contact)
observe how the Raft timing is performing and decide if de-tuning Raft performance or adding to observe how the Raft timing is performing and guide the decision to de-tune Raft performance
more powerful servers might be needed. or add more powerful servers.
* For DNS-heavy workloads, configuring all Consul agents in a cluster with the * For DNS-heavy workloads, configuring all Consul agents in a cluster with the
[`allow_stale`](/docs/agent/options.html#allow_stale) configuration option will allow reads to [`allow_stale`](/docs/agent/options.html#allow_stale) configuration option will allow reads to