[shardingsphere] branch yy2so-patch-2 created (now a7e9547068f)

[yy...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

yy2so pushed a change to branch yy2so-patch-2
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git


      at a7e9547068f Update sharding-cache.en.md

This branch includes the following new commits:

     new a7e9547068f Update sharding-cache.en.md

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[shardingsphere] 01/01: Update sharding-cache.en.md

[yy...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

yy2so pushed a commit to branch yy2so-patch-2
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git

commit a7e9547068f32b964ed2a194d007ba3cb01fa84b
Author: Yacine Si Tayeb <86...@users.noreply.github.com>
AuthorDate: Mon Nov 28 13:43:14 2022 +0800

    Update sharding-cache.en.md
---
 .../yaml-config/rules/sharding-cache.en.md               | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding-cache.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding-cache.en.md
index 32e99faaa7b..a189a31ae29 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding-cache.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding-cache.en.md
@@ -5,14 +5,14 @@ weight = 10
 
 ## Background
 
-This feature is **experimental** and needs to be used with data sharding rule.
-The cache for sharding route will put the logical SQL, the actual parameter value of the shard key, and the routing result into the cache, exchange space for time, and reduce the CPU usage of routing logic.
-
-It is recommended to enable only if the following conditions are met:
-- Pure OLTP scenarios
-- The CPU of the machine which deployed the ShardingSphere process has reached the bottleneck
-- Most of the CPUs are used by ShardingSphere routing logic
-- All SQLs are optimized and each SQL execution could be routed to a single data node
+This feature is **experimental** and needs to be used with the data sharding rule.
+The cache for sharding route will put the logical SQL, the parameter value of the shard key, and the routing result into the cache, exchange space for time, and reduce CPU usage of the routing logic.
+
+We recommend enabling it only if the following conditions are met:
+- Pure OLTP scenarios.
+- The CPU of the machine which deployed the ShardingSphere process has reached the bottleneck.
+- Most of the CPUs are used by ShardingSphere routing logic.
+- All SQLs are optimized and each SQL execution could be routed to a single data node.
 
 If the above conditions are not met, the execution delay of SQL may not be significantly improved, and the memory pressure will be increased.