Project

General

Profile

Actions
Copy link

Feature #48

closed

perform load test on the fully integrated system

Added by chin-yeh about 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Chooi-Mey
Category:
-
Target version:
0.6
Start date:
12/01/2010
Due date:
12/02/2010
% Done:

100%

Estimated time:
8:00 h
Spent time:
10:00 h
Resolution:
Fixed

Description

benchmark the following aspects:
  • the maximum number of transaction per second
  • the time taken to complete x number of transactions
besides that, simulate the following system failure scenarios:
  • queue system is falling down when receiving message
  • queue system is falling down when there's some consumer consuming message
Actions
Copy link
 #1

Updated by chin-yeh about 14 years ago

  • Status changed from In Progress to Feedback
  • Assignee changed from chin-yeh to Chooi-Mey
  • % Done changed from 20 to 100
  • Resolution set to Fixed
Actions
Copy link
 #2

Updated by Chooi-Mey about 14 years ago

Based on discussion, while queue pool is full (during peak time) till not able to accept any new incoming request, instead of request is wait till no end which will impact on frontend app waiting time, go for approach that drop the request packet or set the request timeout. As request has already been stored in Event Log table, which can be pick up for re-try during re-try daemon execution later.

Please test on the approach of drop packet/request timeout setting.

Actions
Copy link
 #3

Updated by chin-yeh about 14 years ago

Change the policy from BLOCK to DROP when reach the maximum size of message in a queue. If maximum size is reached, all of the subsequent message will be dropped.

There is a jmeter script to verify the scenario:

http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/jmeter/qconnector_max_queue.jmx

Steps to execute the jmeter script:
  1. copy the script to your local machine
  2. login to 192.168.2.13
    1. cd to /opt/jboss-5.1.0.GA/server/default-with-hornetq/deploy
    2. rename the ws-mimic.war to ws-mimic.war.bak
      • to avoid any applications to consume the test messages
  3. launch jmeter and execute the script
    • press Ctrl + r or Run -> Start
  4. after the test, perform:
    1. cd to /opt/jboss-5.1.0.GA/server/default-with-hornetq/deploy
    2. rename the ws-mimic.war.bak to ws-mimic.war
      • to restore the application
    3. go to this URL, http://192.168.2.13:8180/jmx-console/HtmlAdaptor?action=inspectMBean&name=org.hornetq%3Amodule%3DCore%2Ctype%3DQueue%2Caddress%3D%22jms.queue.RequestQueue%22%2Cname%3D%22jms.queue.RequestQueue%22
      1. invoke the removeMessages() operation to remove all test messages
Actions
Copy link
 #4

Updated by Chooi-Mey over 13 years ago

  • Status changed from Feedback to Closed
Actions
Copy link

Also available in: Atom PDF