zhengyangyong commented on a change in pull request #47: General development dir translation and include img URL: https://github.com/apache/incubator-servicecomb-docs/pull/47#discussion_r212552839
########## File path: java-chassis-reference/en_US/general-development/reactive.md ########## @@ -94,45 +94,45 @@ public CompletableFuture<String> hello(@PathVariable(name = "name") String name) } ``` -与此对应的处理流程如下： +The corresponding processing flow is as follows:  -* 与传统流程不同的是，所有功能都在eventloop中执行，并不会进行线程切换 +* Unlike traditional processes, all functions are executed in the eventloop and no thread switching is performed. -* 橙色箭头走完后，对本线程的占用即完成了，不会阻塞等待应答，该线程可以处理其他任务 +* After the orange arrow is finished, the occupation of this thread is completed, and it will not block waiting for response. The thread can handle other tasks. -* 当收到远端应答后，由网络数据驱动开始走红色箭头的应答流程 +* After receiving the remote response, the network data drive starts to take the red arrow response process -* 只要有任务，线程就不会停止，会一直执行任务，可以充分利用cpu资源，也不会产生多余的线程切换，去无谓地消耗cpu。 +* As long as there are tasks, the thread will not stop, the task will be executed all the time, you can make full use of the cpu resources, and will not generate redundant thread switching, to consume the CPU unnecessarily. -因为同步模式下，需要大量的线程来提升并发度，而大量的线程又带来线程切换的额外消耗。 +Because in synchronous mode, a large number of threads are needed to increase the degree of concurrency, and a large number of threads bring additional consumption of thread switching. -测试数据表明，reactive模式，只需要消耗同步模式不到一半的cpu，即可达到或超过同步模式的tps，并且时延更低。 +The test data shows that the reactive mode only needs to consume less than half of the CPU of the synchronous mode. And can reach or exceed the tps of the synchronous mode, and the delay is lower. -## 混合Reactive机制 +## Hybrid Reactive Mechanism -Reactvie要求：所有在eventloop中执行的逻辑，不允许有任何的阻塞动作，包括不限于wait、sleep、巨大循环、同步查询DB等等。 +Reactive requires that all logic executed in the eventloop does not allow any blocking actions, including not limited to wait, sleep, large loops, synchronous query DB, and so on. Review comment: including not limited 有点生硬 ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
