FudanSELab/train-ticket

Qestion about response time of ticket searching

Zenghao-CQ opened this issue · 1 comments

Hey guys! Thanks for your brilliant work on TrainTicket.
I am trying to loadtest the search function of TrainTicket, deployed on kubernetes, however even i remove all "resource" field in the yamls, the response time keeps higher than 400ms. This is what i did:

  1. I deploy Traintickt on a k8s cluster using command kubectl apply -f quickstart-k8s
  2. I use hey to loadtest search api by 20 request per second
  3. However the response time(average and p95) keeps higher than 400ms, which is much higher than your paper
  4. Here is my result using kiali:
    微信图片_20220911192843

Performance issues are also a major challenge right now, so perhaps you could use better servers for clustering.