You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "yangyongzheng (JIRA)" <ji...@apache.org> on 2018/02/08 10:52:00 UTC
[jira] [Commented] (SCB-326) Using the EventManager directly
without creating another wrapper
[ https://issues.apache.org/jira/browse/SCB-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356789#comment-16356789 ]
yangyongzheng commented on SCB-326:
-----------------------------------
I had make a test to compare two way performance,result below :
=====================================================================
Custom wapper: can reach 1,000,000 tps and latency is abount 1ms
consumer cpu : about 650%
producer cpu : about 750%
!image-2018-02-08-18-42-40-219.png!
=====================================================================
EventManager: only reach abount 500,000 tps and latency is abount 1.8ms
consumer cpu : about 500%
producer cpu : about 800%
!image-2018-02-08-18-41-03-675.png!
**Think may google EventBus use java Reflection invoke subscribe method and my Custom wapper direct call interface method**
Consumer config:
!image-2018-02-08-18-46-23-679.png!
Producer config:
!image-2018-02-08-18-47-07-285.png!
> Using the EventManager directly without creating another wrapper
> -----------------------------------------------------------------
>
> Key: SCB-326
> URL: https://issues.apache.org/jira/browse/SCB-326
> Project: Apache ServiceComb
> Issue Type: Sub-task
> Components: Java-Chassis
> Affects Versions: java-chassis-1.0.0-m1
> Reporter: yangyongzheng
> Assignee: yangyongzheng
> Priority: Major
> Fix For: java-chassis-1.0.0-m1
>
> Attachments: image-2018-02-08-18-39-42-739.png, image-2018-02-08-18-41-03-675.png, image-2018-02-08-18-42-40-219.png, image-2018-02-08-18-46-23-679.png, image-2018-02-08-18-47-07-285.png
>
>
> Remove custom EventBus because old EventManager with google EventBus is good enough
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)