Performance netflix.zuul-org.apache.http.impl.client.CloseableHttpClient:execute-高响应时间的原因？

来自

/media

的调用图
层上：网关
在节点上：网关

org.springframework.web.servlet.FrameworkServlet:service (method time = 1 ms, total time = 6331 ms)
 HTTPServlet:service:660 (method time = 0 ms, total time = 6330 ms)
  Servlet - dispatcherServlet:doService:943 (method time = 0 ms, total time = 6330 ms)
   Servlet - dispatcherServlet:doDispatch:1040 (method time = 0 ms, total time = 6330 ms)
    Servlet - zuul:service:81 (method time = 0 ms, total time = 6330 ms)
     Servlet - zuul:route:116 (method time = 0 ms, total time = 6329 ms)
      com.netflix.zuul.ZuulRunner:route:96 (method time = 0 ms, total time = 6329 ms)
       com.netflix.zuul.FilterProcessor:route:118 (method time = 0 ms, total time = 6329 ms)
        com.netflix.zuul.FilterProcessor:runFilters:157 (method time = 0 ms, total time = 6329 ms)
         com.netflix.zuul.FilterProcessor:processZuulFilter:193 (method time = 0 ms, total time = 6329 ms)
          com.netflix.zuul.ZuulFilter:runFilter:117 (method time = 0 ms, total time = 6329 ms)
           **org.apache.http.impl.client.CloseableHttpClient:execute:118 (method time = 6329 ms, total time = 6329 ms)**

     Servlet - zuul:postRoute:107 (method time = 0 ms, total time = 1 ms)
      com.netflix.zuul.ZuulRunner:postRoute:87 (method time = 0 ms, total time = 1 ms)
       com.netflix.zuul.FilterProcessor:postRoute:92 (method time = 0 ms, total time = 1 ms)
        com.netflix.zuul.FilterProcessor:runFilters:157 (method time = 0 ms, total time = 1 ms)
         com.netflix.zuul.FilterProcessor:processZuulFilter:193 (method time = 0 ms, total time = 1 ms)
          com.netflix.zuul.ZuulFilter:runFilter:117 (method time = 0 ms, total time = 1 ms)
           Spring Bean - loggingPostFilter:run:53 (method time = 0 ms, total time = 1 ms)
            com.cubic.cumo.apigateway.filters.logging.RequestLogger:logRequest:69 (method time = 0 ms, total time = 1 ms)
             ch.qos.logback.classic.Logger:debug:482 (method time = 0 ms, total time = 1 ms)
              ch.qos.logback.classic.Logger:filterAndLog_0_Or3Plus:383 (method time = 0 ms, total time = 1 ms)
               ch.qos.logback.classic.Logger:buildLoggingEventAndAppend:421 (method time = 0 ms, total time = 1 ms)
                ch.qos.logback.classic.Logger:callAppenders:257 (method time = 0 ms, total time = 1 ms)
                 ch.qos.logback.classic.Logger:appendLoopOnAppenders:270 (method time = 0 ms, total time = 1 ms)
                  ch.qos.logback.core.spi.AppenderAttachableImpl:appendLoopOnAppenders:51 (method time = 0 ms, total time = 1 ms)
                   ch.qos.logback.core.AppenderBase:doAppend:82 (method time = 0 ms, total time = 1 ms)
                    biz.paluch.logging.gelf.logback.GelfLogbackAppender:append:65 (method time = 0 ms, total time = 1 ms)
                     biz.paluch.logging.gelf.logback.GelfLogbackAppender:append:86 (method time = 0 ms, total time = 1 ms)
                      biz.paluch.logging.gelf.logback.GelfLogbackAppender:createGelfMessage:132 (method time = 0 ms, total time = 1 ms)
                       biz.paluch.logging.gelf.MdcGelfMessageAssembler:createGelfMessage:33 (method time = 0 ms, total time = 1 ms)
                        biz.paluch.logging.gelf.GelfMessageAssembler:createGelfMessage:162 (method time = 0 ms, total time = 1 ms)
                         biz.paluch.logging.gelf.GelfMessageAssembler:getValues:216 (method time = 0 ms, total time = 1 ms)
                          biz.paluch.logging.gelf.logback.LogbackLogEvent:getValues:131 (method time = 0 ms, total time = 1 ms)
                           biz.paluch.logging.gelf.logback.LogbackLogEvent:getValue:153 (method time = 0 ms, total time = 1 ms)
                            biz.paluch.logging.gelf.logback.LogbackLogEvent:getSourceClassName:65 (method time = 0 ms, total time = 1 ms)
                             biz.paluch.logging.gelf.logback.LogbackLogEvent:getCalleeStackTraceElement:74 (method time = 0 ms, total time = 1 ms)

定时值为：

ch.qos.logback.classic.spi.LoggingEvent:getCallerData:258（方法时间=0毫秒，总时间=1毫秒）
ch.qos.logback.classic.spi.CallerData:extract:60（方法时间=1ms，总时间=1ms）

---

响应时间长的原因是什么？

您能再讨论一下代码以及在何处/如何部署它吗？@preethi，您对您的问题有什么看法吗？因为我们也看到了这种行为，如果你得到了一些东西，那么请向我提供详细信息，这会很有帮助。你能多讨论一下代码以及在哪里/如何部署它吗？@preethi，你对你的问题有什么看法吗？因为我们也得到了这种行为，如果你得到了什么，那么请提供我的细节，这将是有益的