上增加线程计数高延迟

在以下代码DataGather = endDataGather - beginDataGather花费1.7ms &时间服务响应= service_COMPLETED - service_REQUEST_SENT 从20US变化到200我们（因为它们是模拟虚设上同一LAN因此这样低）现在，如果我增加tomcat8线程从10到200，DataGather增加到150ms +，即使我增加线程从200到1000，那么它甚至增加250 + .Machine规格8核心氙，64GB RAM。当apache基准测试运行时使用-n 40000 -c 100参数来衡量时间，这是由于线程调度/上下文切换还是其他原因造成的？我如何摆脱这种变化？当真正的服务会出现延迟20-100毫秒的图像时，它会保持不变。上增加线程计数高延迟

 public List<ServiceResponse> getData(final List<Service> services, final Data data) { 
      //beginDateGather; 

      final List<ServiceResponse> serviceResponses = Collections.synchronizedList(new ArrayList<>()); 
      try { 
      final CountDownLatch latch = new CountDownLatch(services.size()); 
      Map<Future<HttpResponse>, HttpRequestBase> responseRequestMap = new HashMap<Future<HttpResponse>, HttpRequestBase>(); 

      for (final service service : services) { 
       //creating request for a service 
       try { 
       HttpRequestBase request = RequestCreator.getRequestBase(service, data); 
       //service_REQUEST_SENT 
       Future<HttpResponse> response = client.execute(request, 
        new MyFutureCallback(service, data, latch, serviceResponses)); 
       responseRequestMap.put(response, request); 
       } catch (Exception e) { 
       latch.countDown(); 
       } 
      } 
      try { 
       boolean isWaitIsOver = latch.await(timeout, TimeUnit.MILLISECONDS); 
       if (!isWaitIsOver) { 
       for (Future<HttpResponse> response : responseRequestMap.keySet()) { 
        if (!response.isDone()) { 
        response.cancel(true); 
        } 
       } 
       } 
      } catch (InterruptedException e) { 
      } 
      } catch (Exception e) { 
      } 
      //endDataGather 
      return serviceResponses; 
    } 


    public class MyFutureCallback implements FutureCallback<HttpResponse> { 

     private Service service; 
     private Data data; 
     private CountDownLatch latch; 
     private List<serviceResponse> serviceResponses; 

     public MyFutureCallback(Service service, Data data, CountDownLatch latch, List<ServiceResponse> serviceResponses) { 
      this.service = service; 
      this.data = data; 
      this.latch = latch; 
      this.serviceResponses = serviceResponses; 
     } 

     @Override 
     public void completed(HttpResponse result) { 
      try { 
      ServiceResponse serviceResponse = parseResponse(result, data, service); 
       serviceResponses.add(serviceResponse); 
      } catch (Exception e) { 
      } finally { 
      //service_COMPLETED 
      latch.countDown(); 
      } 
     } 

     @Override 
     public void failed(Exception ex) { 
      latch.countDown(); 
     } 

     @Override 
     public void cancelled() { 
      latch.countDown(); 
     } 
     }

来源

2016-07-23 Shashank

是的，这似乎是由于线程的上下文切换。在这种情况下，增加线程数量将无济于事。您可以使用线程池进行回调。检查此链接，供您参考，并尝试使用.PoolingClientAsyncConnectionManager

How to use HttpAsyncClient with multithreaded operation?

来源

2016-07-23 18:56:32

回调已经由IO Dispacter线程池执行 – Shashank

上增加线程计数高延迟

回答

相关问题