URL pattern Recording Scripts Web_concurrent_start and Web_concurrent_end

LoadRunner function Chinese Translation series of three--concurrent Group
Web_concurrent_start

Grammar:
int Web_concurrent_start ([char * concurrentgroupname,] NULL);
Parameters:
Concurrentgroupname: An identifier for the optional, concurrent group.
NULL: The marker for the end of the parameter list.
return value
Integral type. Returning Lr_pass (0) indicates success, and returning Lr_fail (1) indicates failure.
Description
The Web_concurrent_start function is a token of the start of the concurrency group. All functions in the group are executed concurrently. The end Web_concurrent_end function for the concurrent group. The functions that can be included in a concurrency group are: Web_url, Web_submit_data, Web_custom_request, Web_create_html_param, WEB_CREATE_HTML_PARAM_EX, Web_ Reg_save_param, Web_add_header.
The functions in the concurrency group are not executed immediately. At the beginning of the concurrency group, all functions are first recorded, and when the concurrency group ends, all functions execute concurrently.
All Web users, WAP users in HTTP mode hold this function. This function is not supported for WAP virtual users running in wireless Session Protocol (WSP) playback mode.
Web_concurrent_start

Grammar:
int web_concurrent_end (reserved);
Parameters:
Reserved: the reserved field for the extension.
return value
Integral type. Returning Lr_pass (0) indicates success, and returning Lr_fail (1) indicates failure.
Description
Web_concurrent_end, the tag for the end of the concurrent group. When the script executes, it encounters the Web_concurrent_end function, starting the function of executing all the records concurrently.
The functions in the concurrency group are not executed immediately. At the beginning of the concurrency group, all functions are first recorded, and when the concurrency group ends, all functions execute concurrently.
The number of functions that can be executed concurrently is limited, and is set using the concurrent connection of the run-Time Settings-netword tab.

Many places have not explained this thing clearly. It's actually easier to understand. It's the concept of concurrency groups that knocks people off.

To put it simply:
These two functions are labeled a page request in the URL, note: Here I'm talking about the page, not the request.
In LR request a page, because of the way of recording by using the URL, the elements in a page are divided into several web functions to do processing. Therefore, Web_concurrent_start and Web_concurrent_end are implemented in LR. The purpose of the implementation is to:
From the Web_concurrent_start start tag, when the script runs to Web_concurrent_start, subsequent scripts are not executed immediately until Web_concurrent_end appears. To execute all the scripts in the middle.
The so-called concurrency Group also refers to the implementation of this set of functions together.

If you replace it with Lr_start_transaction and lr_end_transaction, the script can run through it all. The middle script is executed from top to bottom, not together.
The others have no effect.

URL pattern Recording Scripts Web_concurrent_start and Web_concurrent_end