[GitHub] [incubator-dubbo] stoneapple opened issue #2674: Dubbo压测或者大流量线上交易时，消费方耗时远大于提供方耗时

["stoneapple (GitHub)" <gi...@apache.org>]

        不知道各位Dubbo的用户及官方的朋友，有没有遇到或者听过这样的例子。
提供方执行很快，但是消费方却需要很长的时间，有时候就直接超时了，提供方可能1s不到，消费方需要等到几十秒然后超时了，这个场景下gc，cpu看了都还好，之前有抓包提供方返回的报文在交换机上就很迟发出来了。
       有没有遇到相似的，或者有分析思路。

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/2674 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] jasonjoo2010 commented on issue #2674: When Dubbo is measured with large load, the consumer spends much more time than the provider.

["jasonjoo2010 (GitHub)" <gi...@apache.org>]

Do you have the actually QPS for each method invocation?

If you have some `hot service` considering to separate it to a new connection with "connection".
Dubbo's single connection model is designed for small consumers compared with less providers. But if you suffered much heavy traffic on it you should try increasing the number of connections.

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/2674 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] chickenlj commented on issue #2674: Dubbo压测或者大流量线上交易时，消费方耗时远大于提供方耗时

["chickenlj (GitHub)" <gi...@apache.org>]

Do you have the statistics recording the timestamp of the following event?
* Client sent the request
* Server received the request
* Server sent the response
* Client received the response

Also, I got one blog that may help you, shortly conclude is, monitor your network load, open more keep-alive connections if necessary.
https://my.oschina.net/u/1378920/blog/739399

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/2674 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] zonghaishang commented on issue #2674: When Dubbo is measured with large load, the consumer spends much more time than the provider.

["zonghaishang (GitHub)" <gi...@apache.org>]

1. 看抓包`sudo tcpdump -i any -vvvnnttttSs0 port 20880(端口) -w dump.pcap`
然后用wireshark分析报文，可以看到时间

2. 用arthas看下服务调用耗时，https://github.com/alibaba/arthas/blob/master/README_CN.md 和 https://alibaba.github.io/arthas/trace.html

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/2674 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] zonghaishang commented on issue #2674: When Dubbo is measured with large load, the consumer spends much more time than the provider.

["zonghaishang (GitHub)" <gi...@apache.org>]

1. 看抓包`sudo tcpdump -i any -vvvnnttttSs0 port 20880(端口) -w dump.pcap`
然后用wireshark分析报文，可以看到时间

或者 网卡信息查看linux nicstat

2. 用arthas看下服务调用耗时，https://github.com/alibaba/arthas/blob/master/README_CN.md 和 https://alibaba.github.io/arthas/trace.html

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/2674 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] beiwei30 commented on issue #2674: When Dubbo is measured with large load, the consumer spends much more time than the provider.

["beiwei30 (GitHub)" <gi...@apache.org>]

> 之前有抓包提供方返回的报文在交换机上就很迟发出来了。
这种情况优先看下两端的网卡，是不是已经打满，重传率高不高，等等

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/2674 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] cvictory commented on issue #2674: When Dubbo is measured with large load, the consumer spends much more time than the provider.

["cvictory (GitHub)" <gi...@apache.org>]

I think you can give us a demo that can reproduce this issue.
That will be help us large time to reproduce this issue.


[ Full content available at: https://github.com/apache/incubator-dubbo/issues/2674 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [incubator-dubbo] beiwei30 commented on issue #2674: When Dubbo is measured with large load, the consumer spends much more time than the provider.

["beiwei30 (GitHub)" <gi...@apache.org>]

> 之前有抓包提供方返回的报文在交换机上就很迟发出来了。

这种情况优先看下两端的网卡，是不是已经打满，重传率高不高，等等

[ Full content available at: https://github.com/apache/incubator-dubbo/issues/2674 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org