Question posted in
Some documentation to get you started can be found here.

HTTPD response time is increasing after 90 TPS – Apache

I am doing load test to tune my apache to server maximum concurrent https request. Below is the details of my test.

System

  1. I dockerized my httpd and deployed in openshift with pod configuration is 4CPU, 8GB RAM.
  2. Running load from Jmeter with 200 thread, 600sec ramup time, loop is for infinite. duration is long run (Jmeter is running in same network with VM configuration 16CPU, 32GB RAM ).
  3. I compiled by setting module with worker and deployed in openshift.

Issue

  1. Httpd is not scaling more than 90TPS, even after tried multiple mpm worker configuration (no difference with default and higher configuration)
    2.Issue which i’am facing after 90TPS, average time is increasing and TPS is dropping.

Please let me know what could be the issue, if any information is required further suggestions.

Tags:

2

Answers


  1. 0

    I don’t have the answer, but I do have questions.

    1/ What does your Dockerfile look like?

    2/ What does your OpenShift cluster look like? How many nodes? Separate control plane and workers? What version?

    2b/ Specifically, how is traffic entering the pod (if you are going in via a route, you’ll want to look at your load balancer; if you want to exclude OpenShift from the equation then for the short term, expose a NodePort and have Jmeter hit that directly)

    3/ Do I read correctly that your single pod was assigned 8G ram limit? Did you mean the worker node has 8G ram?

    4/ How did you deploy the app — raw pod, deployment config? Any cpu/memory limits set, or assumed? Assuming a deployment, how many pods does it spawn? What happens if you double it? Doubled TPS or not – that’ll help point to whether the problem is inside httpd or inside the ingress route.

    5/ What’s the nature of the test request? Does it make use of any files stored on the network, or "local" files provisioned in a network PV.

    And,

    6/ What are you looking to achieve? Maximum concurrent requests in one container, or maximum requests in the cluster? If you’ve not already look to divide and conquer — more pods on more nodes.

    Login or Signup to reply.
  2. 0

    Most likely you have run into a bottleneck/limitation at the SUT. See the following post for a detailed answer:

    JMeter load is not increasing when we increase the threads count

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search