Advanced Application Models - Configuring Custom Applications

Session 1419
Advanced Application Models Configuring Custom Applications

Application and Server Performance
Copyright 2003 OPNET Technologies, Inc. Confidential, not for distribution to third parties.
1419 Advanced Application Models Configuring Custom Applications
Agenda
Custom application overview Custom application workflow Breaking down an application into tasks and phases Task configuration Lab 1: modeling a 3-tier e-commerce application Task scheduling Connection reuse Lab 2: demonstrate connection reuse Using backend custom application Lab 3: demonstrate backend CA
Miscellaneous: custom application over IP multicast, ACE Troubleshooting Lab 4: troubleshoot misconfigurations
Why Model Applications?

Application behavior is what the end-users see
Infrastructure, deployment is transparent to the users Better applications Better user satisfaction Better business
This companys website is fast!!!
This companys website is lousy!!
VS
Why This Session?

It is important to model applications as accurately as possible
In OPNET
Standard applications Predefined application behavior like request/response characteristics, scheduling, etc. Model typical behavior of the commonly seen day-to-day apps HTTP, Email, Rlogin, Telnet, Voice, Video, Database Custom applications Model specific behavior User has control to define the behavior of the application Can configure request/responses, scheduling, connections, etc Flexible, powerful, and generic
We discuss Custom Application !

Applications
Client-server applications Examples: HTTP, FTP Peer-peer applications
REQUEST RESPONSE REQUEST RESPONSE REQUEST RESPONSE
Examples: voice, video

Multi-tier applications
1
REQUEST
4
REQUEST
3
RESPONSE
RESPONSE
Examples: web-based applications, e-commerce, home-grown applications
Multi-tier Applications
Functionality is divided into separate tiers or levels A single successful instance of the application consists of multiple transactions A transaction consists of exchanges (request/response sequences) at the same logical level Tiers can be located on the same computer or on separate computers.
Tier-1 transaction Tier-2 transaction REQUEST REQUEST RESPONSE RESPONSE
Tier-3 transaction RESPONSE
Custom Application
Can be used to model client-server, peer-peer, multi-tier applications Business: E-commerce, Medical Imaging, etc. Enterprise: ERP, CRM, etc. Defense: Command control, Recon data collection, etc. Home-grown
OPNET Application Architecture

Profiles
Describe user behaviour
Applications
Define application configuration
Tasks
Describe basic unit of user activity
Custom application
Phases
Define communication patterns within each task
Profiles
Profile = collection of applications Describes activity patterns of
An individual user A group of users
Engineer Engineer Engineer Marketing department
CFO
CEO
Help desk
Profile Definition
10
Applications in Profiles
defined in
I have the definitions of the following applications: Database Access (Light) Email (Light) Web Browsing (Light) FTP
11
Custom Application Definition
12
Agenda
Custom application overview Custom application workflow Breaking down an application into tasks and phases Task configuration Lab 1: modeling 3-tier e-commerce application Task scheduling Connection reuse Lab 2: demonstrate connection reuse Using back-end custom application Lab 3: demonstrate backend CA
Miscellaneous: custom app over IP multicast, ACE Troubleshooting Lab 4: troubleshoot misconfigurations
13
Configuring Standard Application Models: Workflow

Configure applications
Define profiles
Configure servers/peers
Deploy Profiles
14
Configuring Custom Application: Workflow

Break down the application Configure tasks Configure custom app
Define Profiles Covered more in 1418
Configure tiers
Deploy profiles
15
Agenda
Custom application overview Custom application workflow Breaking down an application into tasks and phases Task configuration Lab 1: modeling 3-tier e-commerce application Task scheduling Connection reuse Lab 2: demonstrate connection reuse Using custom application Lab 3: demonstrate backend CA
16
Breakdown of the Application

1. Identify the tiers
For example, an online e-commerce application might involve Client Web server Authentication server Database server
17
Breakdown of the Application (cont.)

2. Identify the independent tasks involved that make up a successful instance of the application
For example, buying a book online = login + purchase + logout
LOGIN
PURCHASE
LOGOUT
CUSTOM APPLICATION
18

3. In each task, identify separate actions that accomplish the task
login = connect + authenticate + reply
LOGIN
PURCHASE
LOGOUT
CUSTOM APPLICATION
CONNECT
AUTHENTICATE
REPLY
LOGIN
19

4. Break each phase into a sequence of requests/responses and decide on the request/response pattern (between tiers identified in step 1)
authenticate = 1 request + 1 pkt/request + 1 KB/pkt + 1 response + 1pkt/response + 0.5 KB/pkt
LOGOUT
LOGIN
PURCHASE
CUSTOM APPLICATION
CONNECT
AUTHENTICATE
LOGOUT
LOGIN
Request
Response
20

5. Decide on the parameters of the request/response packets, inter-request time, inter-response time, timeout properties in each phase, etc.
Initialization time / think time
Phase
Request Response
Inter-request time
Response Inter-packet time
21

Break down the application Configure tasks
Configure custom app
Define Profiles
Configure Servers/Peers
Deploy profiles
22
Agenda
Custom application overview Custom application workflow Breaking down an application into tasks and phases Task configuration Lab 1: modeling 3-tier e-commerce application Task scheduling Connection reuse Lab 2: demonstrate connection reuse Using custom application Lab 3: demonstrate backend CA
23
Task Configuration
24
Task Configuration: Task Definition Object
25
Phase Configuration
Manual Configuration OR ACE
26
Task Configuration: Manual Task Attributes

Phase Name + Statistical Group Name Start Phase After (Specifies dependency) Source (Symbolic) Destination (Symbolic) Source->Dest Traffic Dest->Source Traffic REQ/RESP Pattern End Phase When (Specifies dependency) Timeout Properties Transport Connection (TCP/UDP)
27
Task Configuration: Phase Name

Identifies the Phase Identifies the statistics for the Phase
28
Task Configuration: Start Phase After

The starting time of a phase can be specified in 3 different ways
Independent (the source does not depend on the completion of another phase, so the start phase after is set to Application Starts) Previous Phase Ends (sequential phase execution) Some specific phase ends (provide valid Phase Name after which this phase starts)
29
Task Configuration: Source

This attribute specifies the symbolic name of the node that acts as a source for the corresponding phase
3 Special values (no extra symbol resolution needed):

Originating Source The phase starts on the node that supports the profile containing this custom application Previous Source The node that was the source of the previous phase acts as the source Previous Destination The previous phases destination acts as the source for this phase
30
Task Configuration: Destination

This attribute specifies the symbolic name of the node that acts as a destination for the corresponding phase
4 Special values (no extra symbol resolution needed):

Originating Source Previous Source Previous Destination Not Applicable for processing phases
31
Task Configuration: Source->Dest Traffic

Initialization Time
Time spent in the beginning of the phase, before any packets are sent out If no requests are sent, then this is a processing phase
Phase 2
Phase 1 TASK
Requests Responses 32
Task Configuration: Dest->Source Traffic

Inter-response Time
Explicit time that server will spend for each response packet Computed at server: set to Use Server CPU
Phase
Request
Response
33
Task Configuration: REQ/RESP Pattern

This attribute accomplishes the scheduling of request response sequences
Serial : next request is not sent out until response for previous request arrives
Request Response
Phase
time
Inter-request time
Concurrent : requests are sent out independent of arriving responses

Request Response
Phase
time
Inter-request time
34
Task Configuration: End Phase When

End Phase When
Final Request Leaves Source (phase ends at a in the figure) Final Request Arrives at Destination (phase ends at b in the figure) Final Response Leaves Destination (phase ends at c in the figure) Final Response Arrives at Source (phase ends at d in the figure)
Source Destination Request Response
a b c d
35
Task Configuration: Timeout Properties

Timeout Properties
Sets time limit on phase durationphase completes after T seconds, whether or not all transactions are complete within the phase Useful for recovery from lost packets/aborted connections After timeout, execute either next phase or next task
Request
T sec
Response
Source
Destination
36
Task Configuration: Other Task Attributes

Transport Connection (TCP/UDP)
Each phase can use either TCP/UDP/FC as transport protocol Connections can only be reused for TCP Each phase can open up to N connections, where N is the connection limit
37
Agenda
38
Lab 1: Modeling Multi-tier Application

The application we are want to model is a multi-tier e-commerce application. A user (in Los Angeles) is trying to buy a book online from a retailer (in Seattle). The retailers front-end server interacts with a couple of other servers located elsewhere (authentication server in San Francisco and database server in Phoenix).
39
Lab 1: Modeling Multi-tier Application (cont.)

First identify the tiers
Client Web Server Authentication Server Inventory Server
Identify the tasks involved

Login Purchase Logout
40

Split the tasks into phases
Login Connect Authenticate Reply Purchase Surf Select Checkout Update customer database Update inventory Confirm checkout Logout Disconnect
41

Model the request/response details in each phase
Task: Login Task Response Time > 2 + 3 + 0.8 + 1 = 6.8 sec
Client Web Server Init time: 2 seconds 1024 bytes Phase Connect Delay: 3 seconds 1024 bytes 512 bytes Time 512 bytes Phase Reply Phase Authenticate Delay: 1 second Response Time : 0.8 seconds Authentication Server Database Server
42
Lab 1: Modeling Multi-tier Application Task: Purchase (cont.)

Client Phase Surf Web Server
Task Response Time > 25*9 + 3 + 5 + 0.5 + 1 + 0.5 + 1 = 236 sec

Authentication Server Database Server
Request size: 5120 bytes Response size: 51200 bytes
Response Time for each response: 3 seconds
Inter-req time: 25 seconds Time
10 requests + 10 responses
2048 bytes Phase Select 3072 bytes init time: 5 sec init time:0.5 sec Phase Checkout_confirm 1024 bytes 512 bytes
Phase Checkout 5120 bytes 1024 bytes
Phase Transaction_cust Response Time 1sec 5120 bytes 1024 bytes
init time: 0.5 sec
Phase Transaction_inv
43

Task: Logout Task Response Time > 2 sec
Client Web Server 1024 bytes 512 bytes Phase Disconnect Time Response Time : 2 seconds Authentication Server Database Server
44

Total time taken by a single instance of custom application = Time to Login + Time to Purchase + Time to Logout > 6.8 + 236 + 2 sec = 244.8 sec
We expect the total time of the application to be at least 244.8 sec
45
Break
46
Agenda
47

Break down the application Configure tasks Configure custom app
Define Profiles
Configure tiers
Deploy profiles
48
Custom App Configuration
49
Configure Custom App: Task Scheduling
50
Configure Custom App: Task Scheduling (cont.)

Three ways to schedule tasks
Serial (Ordered) All tasks are executed in the order specified in the task list of Task Description attribute
Phase 1.1 Phase 1.2
Phase1.3
Phase2.1
Phase3.1 Phase2.2
TASK 1
TASK 2
TASK 3
CUSTOM APPLICATION
time
51

Concurrent All the tasks start simultaneously, as soon as the application starts
Phase 1.1 Phase 1.2
Phase1.3
TASK 1
Phase2.1 Phase2.2
TASK 2
Phase3.1
TASK 3
CUSTOM APPLICATION
time
52

Serial (Random) The tasks are executed one after another but in a random order The exact number of tasks can be specified in the Number of Used Tasks field
Phase 1.1 Phase 1.2
Phase1.3
Phase2.1 Phase3.1 Phase2.2
TASK 1
TASK 3
TASK 2
CUSTOM APPLICATION
time
53
Agenda
54
Configure Custom App: Connections

New connection per request
Request Response
Phase1
Phase2 TASK
time
55
Configure Custom App: Connections (cont.)

Reuse connections across requests
Request Response
Phase1
Phase2 TASK
time
56
Configure Custom App: Connections (cont.) Response

Reuse connections across phases
Request
Phase1
Phase2 TASK1
Phase1
Phase2 TASK2
CUSTOM APPLICATION
time
57
Configure Custom App: Connections (cont.)

Reuse connection across tasks
Request Response
Phase1
Phase2 TASK1
Phase1
Phase2
TASK2 CUSTOM APPLICATION
58
Configure Custom App: Connection Management

Hierarchy of attributes that decides connection reuse policy (in decreasing order of priority)
1. Task Config Object / Manual Configuration / Transport Connection / Policy If set to new connection per request, the next two attributes are ignored Otherwise, connections are used as determined by the policies below
59
Configure Custom App: Connection Management (cont.)

2. Task Config Object / Manual Configuration / Transport Connections / Connections / Policy Specifies if connections can be reused across phases or if they should be refreshed after phase
60
Configure Custom App: Connection Management (cont.)

3. Task Config Object / Connection Policy Specifies if connections can be reused across tasks or if they should be refreshed after each task
61
Agenda
62
Lab 2: Demonstrate Connection Reuse

Objective: make all traffic between each pair of tiers reuse the same connection
Refer to the lab manual
63

Break-down the application Configure tasks Configure custom app
Define Profiles
Configure tiers
Deploy profiles
64
Configure Tiers
65
Configure Tiers (cont.)

Assign TPAL addresses to the nodes
Appears as attribute Client Address on workstations Server Addressof servers LAN Server Name on LAN objects
Resolve Destination Preferences

Destination Preferences Resolve symbolic destinations to real destinations Specify a choice of destinations with a selection weight
66
Destination Preferences
Resolves symbol WEB_SERVER to web_server_1 & web_server_2
Resolves symbol DB_SERVER to db_server_1 & db_server_2
67
Destination Preferences Attribute
68
Symbol Resolution
Symbol Resolution is done every time a Task is executed
Once a symbolic name is resolved to a node, the resolution will not change during the execution of the Task If a symbolic name cannot be resolved, custom application logs an error and stops the task execution
69
Contention Modeling
Server Contention Modeled for
Src Dest Traffic: Init Time Dest Src Traffic: Request Processing Time
If Server_Job_Name attribute is set, contention will be modeled using Advanced Server / Mainframe Models
Refer to the Online Documentation on Advanced Server Configuration for details on modeling Advanced Server / Mainframe jobs
Otherwise, the Simple CPU model will be used for contention modeling
Refer to FAQ 1106 for details on configuring the Simple CPU model
70
Source Preferences
Soldier 2 Soldier 1
Commander
Soldier 3
HQ
Independent sources
Set the Start Phase After to Application Starts
71
Source Preferences (cont.)

Identify the nodes that act as the source of any of the phases Specify the source preferences on each node so that the symbol in the source preferences is the same as the symbol of the phase Source that this node supports
72
Available Statistics
73
Agenda
74
Back-end Custom Application

Standard two-tiered applications (Email, FTP, Http, etc.) trigger execution of custom application from the server
1
REQUEST
2 3
RESPONSE
Custom Back-end
Each application request triggers the start of the custom application on the server with a given probability. Once the custom application run is over, a response is sent back to the client.
75
Back-end Custom Application (cont.)

Specific advantages Integration of regular and custom applications Application-specific statistics Improved modeling of complex web applications, web caching, email, etc.
76
Back-end Custom ApplicationAttributes
77
Agenda
Custom Application Overview Custom Application Workflow Breaking-down an application into tasks and phases Task Configuration lab 1: Modeling 3-Tier E-Commerce Application Task Scheduling Connection reuse Lab 2: Demonstrate connection reuse Using back-end custom application lab 3: Demonstrate backend CA
Miscellaneous: Custom app over IP Multicast, ACE Troubleshooting lab 4: Troubleshoot misconfigurations
78
Lab 3: Back-end Custom Application

Refer to the lab manual
79
Agenda
80
IP Multicast / ACE
Custom applications can run over IP Multicast
Simply set the Phase Destination to the IP Multicast address Supported over UDP only Supports only Src Dest Traffic Refer session 1316 for IP Multicast configuration
Integration with ACE

Can import an ACE trace file Custom application will use the trace file to play-back the same behavior The play-back is at the task level Refer session 1209 for ACE
81
Agenda
Custom application overview Breaking down an application into tasks and phases Custom application workflow Task configuration Lab 1: modeling 3-tier e-commerce application Task scheduling Connection reuse Lab 2: demonstrate connection reuse Using custom application to model back-end behavior of servers Lab 3: demonstrate backend CA
82
Troubleshooting Guidelines
1. 2. 3. 4. 5. 6. Check simulation logs Look at the Common problems section of this presentation Use constant distributions to make application deterministic Use detailed Custom Application Statistics (phase, task) Collect application Traffic Sent/Received stats in All Values mode Shows exact size and time data was sent Make sure this is not a network issue Connect an application demand between your client and server See if you get application demand response time statistics Scale down your network Isolate the problem Use User Defined Reports in Scenarios menu Globally visualize attribute settings Use Network Difference Report in Scenarios menu Compare a similar working scenario
83
7. 8. 9.
Troubleshooting: Simulation Logs

Simulation = first place to look Available in DES menu
84
Troubleshooting: Simulation LogsProfile

Profile wont repeat if profile duration is equal to simulation duration
Simulation
Engineer profile Engineer profile
In serial mode, an application will not start if previous application duration is equal to profile duration
Simulation
Engineer profile FTP application HTTP application
85
Troubleshooting: Simulation LogsProfile (cont.)

Profile set on a client doesnt exist
Sorry, I dont know what an engineer is
? ?
Im an engineer
Engineer profile
Service set on server doesnt exist

Im running FTP (Light)
Sorry, I dont know what FTP (Light) is
FTP (Light) application

86
Service set on server doesnt exist
Troubleshooting: Simulation Logs Standard Apps

Profile engineer uses FTP (Light)
Sorry, I dont know what FTP (Light) is
All required application parameters are not configured

FTP (Light) is a FTP application
Sorry, I need more information to use FTP (Light): File size
Inter-request time
87
Destination in phase is not resolved
Troubleshooting: Simulation LogsCustom Apps

Task login has my_destination destination
Sorry, I dont know who the real my_destination is
Source in phase is not resolved

Task login has my_server as source
Sorry, I dont know who the real my_destination is
88
Troubleshooting: Simulation LogsCustom Apps (cont.)

Unknown task in application specification
online_shopping_app uses purchase task s
Sorry, I dont know what purchase is.
Two or more phases with same name
Sorry, I am confused. There are two phases with the same name : connect 89
Common Problems: Simulation Settings

Profile start time + application start time offset and spanning tree algorithm, etc.
I want to send this FTP packet
<
Convergence time of routing protocols
Wait, I dont have a route to the server yet
Profile start time + application start time offset
Simulation end time Common when using exponential distribution with start time and/or start time offset
>
Simulation
Profile start time
Simulation
Engineer profile
Profile start time Application start time offset
90
Common Problems: Profile Settings

If application duration is longer than profile duration, the application will be terminated when the profile is over
Simulation
Engineer profile FTP application
The symbol map Unlimited for profile and application Repeatability has a default inter arrival time of 300 secs
Engineer profile
Engineer profile
Engineer profile
Engineer profile
Etc
300 secs
300 secs
300 secs 91
Common Problems: Custom App Settings

If the traffic for a phase is configured beyond the application duration, that phase is not completed. Also, other phases dependant on this one will not execute.
APP
Phase2.1
Phase2.2
TASK 2
This phase is not executed
In a multi-tier application with phases A->B and B->C, the destination symbol C must be resolved on the node that is destination for phase A->B
Wait, I dont know who C is!!!
?
92
Common Problems: Custom App Settings (cont.)

In the phase definitions, the first phase cannot use the special symbols previous source and previous destination when specifying the source and destination
Please be careful with the first phase!!!
Phases are not executed if a prior phase which precedes these (in dependency) times out and the time-out action is Go to next task
APP
Phase 1.1 Phase1.3 Phase2.1
APP
Phase2.2
Phase3.1
Phase 1.2
TASK 1
TASK 2
TASK 3
Time up!! Going to TASK 3, Phase 2.2 not executed

93
Advanced Troubleshooting
Run OPNET debugger (ODB)
Diagnostic traces
For Custom application type: ltrace gna_ca for task information: ltrace gna_task for connection information: ltrace gna_conn for traffic (requests/responses) information: ltrace gna_traf For all applications: ltrace gna Simple example Start simulation under ODB ODB> ltrace gna_conn ODB> cont This is an advanced technique. For more details, see session 1502 Debugging Simulation Models Introduction
94
TS FAQs
729 769 986 How do I configure a back-end custom application? What is the Task Weight attribute used for in custom applications? Is IP Multicast supported for custom applications?
1160 I dont see any application traffic or I dont see the expected application traffic. How do I troubleshoot my application configuration?
1170 I have configured a custom application and it works fine with the simple CPU model. How do I integrate the custom app with advanced server model?
95
Agenda
Custom application overview Breaking down an application into tasks and phases Custom application workflow Task configuration Lab 1: modeling 3-tier e-commerce application Task scheduling Connection reuse Lab 2: demonstrate connection reuse Using back-end custom application Lab 3: demonstrate backend CA
96
lab 4: Troubleshooting
Objective
Learn how to troubleshoot a custom application setup Refer to the lab manual
97
Take Away Points

Custom application workflow
Breakdown of application Task configuration Symbol resolution
Advanced features
Scheduling Connection reuse
Back-end custom application Troubleshooting
98
Related Sessions
Configuring Application Models Session 1418 Trends in Traffic Modeling Session 1338 Predicting Server Performance Scalability Intro Session 1405 Introduction to Using ACE Session 1209 Planning Application Deployments with ACE Session 1409 Customizing Application Layer Models Session 1509
99
Questions?
100
Thank You
101

Advanced Application Models - Configuring Custom Applications

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Advanced Application Models - Configuring Custom Applications

Caricato da

Copyright:

Formati disponibili

Session 1419

Advanced Application Models Configuring Custom Applications

1419 Advanced Application Models Configuring Custom Applications

1419 Advanced Application Models Configuring Custom Applications

Why Model Applications?

This companys website is fast!!!

This companys website is lousy!!

1419 Advanced Application Models Configuring Custom Applications

Why This Session?

We discuss Custom Application !

1419 Advanced Application Models Configuring Custom Applications

Examples: voice, video

Examples: web-based applications, e-commerce, home-grown applications

1419 Advanced Application Models Configuring Custom Applications

Tier-3 transaction RESPONSE

1419 Advanced Application Models Configuring Custom Applications

1419 Advanced Application Models Configuring Custom Applications

OPNET Application Architecture

1419 Advanced Application Models Configuring Custom Applications

Engineer Engineer Engineer Marketing department

1419 Advanced Application Models Configuring Custom Applications

1419 Advanced Application Models Configuring Custom Applications

1419 Advanced Application Models Configuring Custom Applications

Custom Application Definition

1419 Advanced Application Models Configuring Custom Applications

1419 Advanced Application Models Configuring Custom Applications

Configuring Standard Application Models: Workflow

1419 Advanced Application Models Configuring Custom Applications

Configuring Custom Application: Workflow

Define Profiles Covered more in 1418

1419 Advanced Application Models Configuring Custom Applications

1419 Advanced Application Models Configuring Custom Applications

Breakdown of the Application

1419 Advanced Application Models Configuring Custom Applications

Breakdown of the Application (cont.)

1419 Advanced Application Models Configuring Custom Applications

Breakdown of the Application (cont.)

1419 Advanced Application Models Configuring Custom Applications

Breakdown of the Application (cont.)

1419 Advanced Application Models Configuring Custom Applications

Breakdown of the Application (cont.)

Response Inter-packet time

1419 Advanced Application Models Configuring Custom Applications

Configuring Custom Application: Workflow

Configure custom app

1419 Advanced Application Models Configuring Custom Applications

1419 Advanced Application Models Configuring Custom Applications

1419 Advanced Application Models Configuring Custom Applications

Task Configuration: Task Definition Object

1419 Advanced Application Models Configuring Custom Applications

Manual Configuration OR ACE

1419 Advanced Application Models Configuring Custom Applications

Task Configuration: Manual Task Attributes

1419 Advanced Application Models Configuring Custom Applications

Task Configuration: Phase Name

1419 Advanced Application Models Configuring Custom Applications

Task Configuration: Start Phase After

1419 Advanced Application Models Configuring Custom Applications

Task Configuration: Source

3 Special values (no extra symbol resolution needed):

1419 Advanced Application Models Configuring Custom Applications

Task Configuration: Destination