Skip to content

Commit e36c615

Browse files
committed
update comment
Signed-off-by: Loong <[email protected]>
1 parent 051cdbf commit e36c615

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

linkerd.io/content/blog/accelerate-linker-with-dlb.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ In this way, the workload of all threads can be balanced by Intel DLB and perfec
7575
The best case for Intel DLB-enabled Tokio is high traffic, like ingress. Since Linkerd2 should work with existing ingress solutions such as Nginx Ingress, we deploy the benchmark environment as below:
7676
![dlb-benchmark-env](/uploads/dlb-benchmark-env.png)
7777

78-
In our lab, we compared the baseline of pure Linkerd2-Proxy to the target of Linkerd2-Proxy plus Intel DLB. The result shows that the request per second has been greatly improved and the latency has been reduced.
78+
In our lab, we compared the baseline of pure Linkerd2-Proxy to the target of Linkerd2-Proxy with Intel DLB and the result shows that the request per second has been improved and the latency has been reduced.
7979

8080
## Conclusion
8181

@@ -85,4 +85,4 @@ The fourth-generation Intel Xeon scalable processor, codenamed Sapphire Rapids,
8585

8686
The whole solution is experimental, please contact [me](mailto:[email protected]) for any details if interested.
8787

88-
We firmly believe that with the development of cloud computing and service mesh, solutions combining software and hardware can provide users with higher performance.
88+
We firmly believe that with the development of cloud computing and service mesh, solutions combining software and hardware can provide users with higher performance.

0 commit comments

Comments
 (0)