Latency and Processing Time and Response Time

What is the difference between Latency, Processing Time and Response Time ? 

What is Latency? 

Latency is the delay incurred in communicating a message (the time the message spends “on the wire”).

What is Processing Time?

Processing time is the amount of time a system takes to process a given request, not including the time it takes the message to get from the user to the system or the time it takes to get from the system back to the user.

Processing time can be affected by changes to your code, changes to systems that your code depends on (e.g. databases), or improvements in hardware.

What is Response Time?

Response time is the total time it takes from when a user makes a request until they receive a response.

Response time can be affected by changes to the processing time of your system and by changes in latency, which occur due to changes in hardware resources or utilization.

Latency + Processing Time = Response Time


Uses of Controllers in JMeter

JMeter has two types of Controllers:

  1. Samplers
  2. Logic Controllers


  • Samplers allow JMeter to send specific types of requests to a server.
  • They simulate a user’s request for a page from the target server.
  • For example, you can add a HTTP Request sampler if you need to perform a POST, GET, DELETE on a HTTP service
  • Some useful samplers are:
    – HTTP Request
    – FTP Request
    – JDBC Request
    – BSF Request
    – SOAP/XML Request
    – RPC Requests
FTP Request:
This controller lets you send an FTP “download file” or “upload file” request to an FTP server.

For example, if you want to download a file “Test.txt” from a FTP server under test, you need to configure some parameters in JMeter as figure below-

FTP Request

JMeter will send FTP command to FTP server, and then download a file Test.txt from that server.

HTTP Request:
  • This sampler lets you send an HTTP/HTTPS request to a web server.
  • JMeter send a HTTP request to Google website and retrieve HTML files or image from this website.

HTTP Reuquest

JDBC Request:
  • This sampler lets you execute Database Performance Testing. It sends a JDBC Request (an SQL query) to a database.

JDBC Request

For example, a database server has a field test result stored in a table name test_tbl. You want to query this data from the database server; you can configure JMeter to send a SQL query to this server to retrieve data.


  • Logic Controllers let you control order of processing of Samplers in a Thread.
  • Logic Controllers can change the order of request coming from any of their child elements.
  • Some examples are: For Each Controller, While Controller, Loop Controller, IF Controller, Run Time Controller, Interleave Controller, Throughput Controller, and Run Once Controller.
  • A Loop Controller Control Panel looks like the following figure:

Logic Controller

The following list consists of all the Logic Controllers JMeter provides:

  • Simple Controller
  • Loop Controller
  • Once Only Controller
  • Interleave Controller
  • Random Controller
  • Random Order Controller
  • Throughput Controller
  • Runtime Controller
  • If Controller
  • While Controller
  • Switch Controller
  • For Each Controller
  • Module Controller
  • Include Controller
  • Transaction Controller


  • Listeners: shows the results of the test execution.
  • They can show results in different format such as tree, table, graph or log file

The following list consists of all the Listeners JMeter provides:




  • By default, a JMeter thread will send requests without pausing between each sampler.
  • This may not be what you want. We can add a timer element which will allow us to define a period to wait between each request.



Thanks for viewing and Please share your comments….

What is Thread Group in the Jmeter ?

Thread group in the Test Plan- 

Thread Group: A test plan must have at least one thread group.

Add Thread Group Thread Group


Number of Threads (users): Simulates the number of user(s) or connection(s) to your server application.
Number of Threads: 100 (Number of users connects to target website: 100)

Loop Count: Defines the number of times to execute the test.
Loop Count: 10 (Number of time to execute testing)

Ramp-Up Period: It tells JMeter how long to delay before starting next user.
Ramp-Up Period: 100

For example, if we have 100 users and a 100 second Ramp-Up period, then the delay between starting users would be 1 second (100 users /100 seconds)

Delay request


Scheduler checkbox: Once selected, the Scheduler Configuration section will appear at the bottom of the control panel.

Scheduler Configuration: You can configure the start and end time of running the test.


Thanks for reading. Please share your views–


Introduction to Apache JMeter Performance Testing

Introduction to Apache JMeter:  JMeter works only on two fields:

  1. Test Plan
  2. Workbench

Test Plan and workbench

1.Test Plan:

  • Test Plan defines what to test and how to execute no of steps in jmeter.

For ex: Web application as well as the client server application. It can be viewed as a container for running tests.

  • A test plan must have at least one thread group.
  • A complete test plan will consist of one or more elements such as
  • Thread groups
  • Logic controllers
  • Sample-generating controllers
  • Listeners
  • Timers
  • Assertions
  • Configuration elements.


  • It’s Provide a place to store test elements temporarily.
  • JMeter doesn’t save the content of workbench.
  • JMeter only save the content of Test Plan.
  • No relation with the Test Plans.