Enhancing Vuser Scripts

-
1.   You define transactions to measure the performance of the server. Each transaction measures the time it takes for the server to respond to specified Vuser requests
2.   You configure multiple Vusers to act simultaneously by creating a rendezvous point.
3.   Rendezvous points are only effective in Action section(s)—not init or end.
4.   lr_get_attrib_string - Returns a command line parameter string.
5.   lr_get_host_name - Returns the name of the machine running the Vuser script.
6.   lr_get_master_host_name - Returns the name of the machine running the Controller. Not applicable when working with the HP Business Availability Center.
7.   lr_whoami -Returns the name of a Vuser executing thescript.
8.   lr_debug_message -Sends a debug message to the Output window or the Business Process Monitor log file.
9.   lr_error_message - Sends an error message to the Output window or the Business Process Monitor log files.
10.                lr_get_debug_message - Retrieves the current message class.
11.                lr_log_message- Sends an output message directly to the log file, output.txt, located in the Vuser script directory. This function is useful in preventing output messages from interfering with TCP/IP traffic.
12.                lr_output_message- Sends a message to the Output window or the Business Process Monitor log files.
13.                lr_set_debug_message- Sets a message class for output messages.
14.                lr_vuser_status_message- Sends a message to the Vuser status area in the Controller. Not applicable when working with the HP Business Availability Center.
15.  lr_message- Sends a message to the Vuser log and Output window or the Business Process Monitor log files.
16.  The behavior of the lr_message, lr_output_message, and lr_log_message functions are not affected by the script’s debugging level in the Log run-time settings—they will always send messages.
17.  Synchronization applies to RTE Vuser scripts only. The time that a user waits between performing successive actions is known as the think time.
18.  When you record a Java Vuser script, lr_think_time statements are not generated in the Vuser script.
19.  VuGen uses 32-bit encryption.

Comments

Post a Comment

Popular posts from this blog

Steps to Analyze AWR Report in Oracle

-
Image
Steps to Analyze AWR Report in Oracle AWR -   Automatic   workload repository is a collection of persistent   system performance   statistics   owned by SYS. It resides in SYSAUX   tablespace . By default snapshot are generated once every 60 min and maintained for 7 days . Each snapshot has a unique ID know as "snap_id". Snapshot detail can be found in " dba_hist_snapshot " view.   If we have Database performance issue and not the Database machine, then AWR Report is the place to look at. AWR is not used for real-time performance monitoring like the v$ tables. It is used for historical analysis of performance. AWR complements, but doesnot replace real-time monitoring. Once AWR Report is generated in Oracle, the next task is to analyze it. By going through the AWR Report we can easily solve issues like slow database, high wait events, slow query and many more issues. Even though the report is lengthy, Analyzing or Reading relevant part of AWR Report can
Read more

Vmstat Output explained

-
vmstat : vmstat is a tool in Unix/Linux which is used to Report virtual memory statistics. It shows how much virtual memory there is, how much is free and paging activity. Most important, you can observe page-ins and page-outs as they happen.   vmstat   reports   information about processes, memory, paging, block IO, traps, and cpu activity.   > vmstat procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu-----   r   b    swpd    free    buff   cache         si    so     bi     bo    in    cs us sy id wa st   0   0   21688 12797396 850716 15372668     0     0      3     35     0     0   1   0 99   0   0   0   0   21688 12789292 850716 15372668     0     0      0   1355   883   744   1   0 99   0   0   1   0   21688 12784648 850716 15372676     0     0      0     15 1934 1292   6   0 93   0   0   2   0   21688 12781356 850716 15372736     0     0      0     16 2222 2094   8   1 92   0   0   0   0   21688 12809992 850716 15376880     0
Read more

Verifications and Error Handling in LoadRunner *Web_reg_find and Web_reg_save_param*

-
Verification's and Error Handling Verification points must be inserted into the scripts to verify the application being tested with the load. Verification function that are used in our application are:  Web_reg_find, web_reg_save_param These verification should be outside towards the end of the transaction. Mandatory verification points: ■          Login – whenever there is a login, verification points must be added to verify that the user logged in correctly. ■          Update Transactions – transactions that update the database must be verified that they are successful. ■          Each page should be verified using Web_reg_find function Using Web _ reg_find for verifications. Example: web_reg_find("Text= Main Package","SaveCount=Verify_Count1",LAST); Verification: if (strcmp(lr_eval_string("{Verify_Count1}"),"0")==0) { lr_end_transaction("AddMainPackage", LR_FAIL);  lr_error_message(&q
Read more