From 7e4eccef08c910158ecb0c5a0731cf3efb219f7c Mon Sep 17 00:00:00 2001 From: Wu Sheng Date: Fri, 27 Jul 2018 15:47:21 +0800 Subject: [PATCH] Update a document sentence. --- docs/en/concepts-and-designs/service-agent.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/concepts-and-designs/service-agent.md b/docs/en/concepts-and-designs/service-agent.md index f91c9386d0..a0c624e972 100644 --- a/docs/en/concepts-and-designs/service-agent.md +++ b/docs/en/concepts-and-designs/service-agent.md @@ -14,7 +14,7 @@ Also, we said that the most auto instrument agents are VM based, but actually, y runtime. ## What are limits? -Auto instrument is so cool, then you can create those in compiling time, that you don't depend on VM features, then is there +Auto instrument is so cool, also you can create those in compiling time, that you don't depend on VM features, then is there any limit? The answer definitely **YES**. And they are: @@ -27,7 +27,7 @@ by agent plugin developers. So, there is always a supported list in this kind of Like [SkyWalking Java agent supported list](../setup/service-agent/java-agent/Supported-list.md). - **Across thread can't be supported all the time**. Like we said about **in process propagation**, most codes -run in a single thread per request. But in some other scenarios, they do things in different threads, such as +run in a single thread per request, especially business codes. But in some other scenarios, they do things in different threads, such as job assignment, task pool or batch process. Or some languages provide coroutine or similar thing like `Goroutine`, then developer could run async process with low payload, even been encouraged. In those cases, auto instrument will face problems. -- GitLab