[dubbo-getty] branch improve/delte-handleLoop updated: feat: update benchmark client send message

[alexstocks]

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

alexstocks pushed a commit to branch improve/delte-handleLoop
in repository https://gitbox.apache.org/repos/asf/dubbo-getty.git


The following commit(s) were added to refs/heads/improve/delte-handleLoop by 
this push:
     new cc79634  feat: update benchmark client send message
     new 8dbc1b3  Merge pull request #66 from georgehao/improve/delte-handleLoop
cc79634 is described below

commit cc796347d2609cb44064c0577dc07ffec209980d
Author: georgehao <haohong...@gmail.com>
AuthorDate: Wed Jun 30 20:05:34 2021 +0800

    feat: update benchmark client send message
---
 benchmark/client/main.go      | 2 +-
 benchmark/loop_client/main.go | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/benchmark/client/main.go b/benchmark/client/main.go
index 2484cfb..532493b 100644
--- a/benchmark/client/main.go
+++ b/benchmark/client/main.go
@@ -257,5 +257,5 @@ func (h *PackageHandler) Write(ss getty.Session, p 
interface{}) ([]byte, error)
 }
 
 func buildSendMsg() string {
-       return "如果扫描程序匹配了一行文本并且没有遇到错误，则 sc.Scan() 方法返回 true 
。因此，只有当扫描仪的缓冲区中有一行文本时，才会调用 for 循环的主体。这意味着我们修改后的 CountLines 
正确处理没有换行符的情况，并且还处理文件为空的情况。"
+       return "Now we know what the itables look like, but where do they come 
from? Go's dynamic type conversions mean that it isn't reasonable for the 
compiler or linker to precompute all possible itables: there are too many 
(interface type, concrete type) pairs, and most won't be needed. Instead, the 
compiler generates a type description structure for each concrete type like 
Binary or int or func(map[int]string). Among other metadata, the type 
description structure contains a list of the met [...]
 }
diff --git a/benchmark/loop_client/main.go b/benchmark/loop_client/main.go
index 60d6dc9..d96094a 100644
--- a/benchmark/loop_client/main.go
+++ b/benchmark/loop_client/main.go
@@ -205,5 +205,5 @@ func (h *PackageHandler) Write(ss getty.Session, p 
interface{}) ([]byte, error)
 }
 
 func buildSendMsg() string {
-       return "如果扫描程序匹配了一行文本并且没有遇到错误，则 sc.Scan() 方法返回 true 
。因此，只有当扫描仪的缓冲区中有一行文本时，才会调用 for 循环的主体。这意味着我们修改后的 CountLines 
正确处理没有换行符的情况，并且还处理文件为空的情况。"
+       return "Now we know what the itables look like, but where do they come 
from? Go's dynamic type conversions mean that it isn't reasonable for the 
compiler or linker to precompute all possible itables: there are too many 
(interface type, concrete type) pairs, and most won't be needed. Instead, the 
compiler generates a type description structure for each concrete type like 
Binary or int or func(map[int]string). Among other metadata, the type 
description structure contains a list of the met [...]
 }