Detailed explanation of the whole process of coding's pressure measurement operation

Operation Overview

One 、 Preparation before pressure test

1. Pressure test cluster purchase and pressure test service deployment

Jmeter-Suite Pressure test tool deployment document - cloud + Community - Tencent cloud

2. structure Coding project

Coding Platform project construction guide - cloud + Community - Tencent cloud

3. perform demo Script validation cluster

perform demo The script needs to confirm the following two things before verifying the pressure test cluster ：

（1） Confirm the pressure measurement cluster kubeconfig The file has been uploaded to Coding The warehouse kubeconfig Under the table of contents .

（2） confirm Coding Pressure measurement construction machine ip It has been added to the white list of cluster Internet access .

After confirmation , Start to perform the following steps to verify ：

（1） Get into Coding Click after the project “ Continuous integration -> Build a plan ”, Select the construction plan of the configured pressure test cluster , Click on “ Build immediately ”

（2） Build the configuration page now , Refer to section 5 Chapter pressure measurement execution , Perform the pressure test task according to the default configuration , Execute the in the warehouse testScript/Test.jmx Script , Launch Baidu website 100 Concurrent piezometry , Click on “ Build immediately ”

（3） Refer to section 9 Check the pressure test results in Chapter , As shown in the figure below , Can see grafana The panel can show QPS、 Error rate and so on , Indicates that debugging is complete .

Two 、 Pressure measurement execution process

4. Upload the pressure test script & Data files

Be careful ： Upload to coding Script of the platform , You need to add a new one in the back-end listener tag,TAG_Random ${__Random(0000000000,9999999999,)}, Details are as follows ：

（1） Get into Coding Click after the project “ Code warehouse ”, Upload the pressure test script to teamSrcipt Under the table of contents , Click on “teamSrcipt” The three points on the right , Click on “ Upload ”

（2） Click on “ Select File ” Area , Select the script that has been transferred locally to upload

（3） After uploading the script , Click on “ confirm ”

5. Pressure test execution

（1） After entering the project, click “ Continuous integration -> Build a plan ”, Click the red position of the pressure measurement execution .

（2） The following window pops up , Reference resources “ Parameters, ” The table modifies the parameters , Then click “ Build immediately ” Start the pressure test task .

Parameters, ：

Parameters	Parameter values	Parameter description
KUBECONFIG	Customize	In the code warehouse kubecofig Absolute path ; If the cluster has been configured , Then there is no need to modify the pressure measurement .
NAME_SPACE	Default default	There is no need to modify
TEST_PATH	Customize	The pressure test script to be executed is Coding The address in the warehouse
Number_Of_Nodes	Customize	Indicates the number of nodes that need to be started , Total concurrent number = Number of nodes x The number of concurrency configured by the script , You can fill in the number of nodes to be started as needed , The maximum number will not be greater than the number of pressure measuring machines , The default is 10
Upload_Data_File	Choose one of two options ● Upload data files ● Do not upload data files （ The default value is ）	Choose whether to upload data files , Included in the code warehouse all txt、csv and jar file , You need to select “ Upload data files ”, If there is no new data file in the future, it will not be uploaded by default （ Such as pod restart 、 The pressure measurement cluster has just started , Need to upload again ）, It is recommended to clean the data files in the warehouse regularly , Ensure that documents can be uploaded quickly .
Split_File	Choose one of two options ● Split data file ● Do not split data files （ The default value is ）	Choose whether to split the data file , Included in the code warehouse all txt and csv file , If you choose “ Split data file ”, You don't have to choose “ Upload data files ”, It is recommended to use , For example, repeated data pressure testing leads to business exceptions , You can choose to split the data file （ Be careful ：① For example, the number of data files is less than the number of nodes , Only the number of nodes corresponding to the number of data files will be split , Nodes that exceed the number of entries will have no data files ;②pod restart 、 The pressure measurement cluster has just started , Need to be split again ）, It is recommended to clean the data files in the warehouse regularly , Ensure that documents can be uploaded quickly .

6. Pressure measurement stop

（1） After entering the project, click “ Continuous integration -> Build a plan ”, Click the red position where the pressure measurement stops .

（2） The following window pops up , Reference resources “ Parameters, ” The table modifies the parameters , Then click “ Build immediately ” Stop the pressure test task .

Parameters, ：

Parameters	Parameter values	Parameter description
KUBECONFIG	Customize	In the code warehouse kubecofig Absolute path ; If the cluster has been configured , Then there is no need to modify the pressure measurement .
NAME_SPACE	Default default	There is no need to modify

3、 ... and 、 Check the pressure measurement process data

7. Check the pressure measurement data panel

7.1 Get data panel information

（1） After entering the project, click “ Continuous integration -> Build a plan ”, After performing the pressure test task, click the build task

（2） Click to enter the recent build task

（3） After entering the task, click “ Address of pressure test result panel ” Conduct grafana Address check , The account and password are also inside

Be careful ： If the account password is incorrect, please try the password admin Or please contact the students who deploy the pressure testing service .

7.2 View the data panel

（1） Click to get the panel link , Enter account / Password to access grafana, Click on the top left corner “Home”

（2） Select the first one after entering , Click to enter

（3） Select the “application” You can see the latest pressure test results ,“transaction” You can select the tested interface , Pressure measurement time can be selected in the upper right corner , View historical pressure measurement data .

8. Check the log

8.1 Check the execution process log

（1） After the pressure test execution task is completed, click the task just executed

（2） Click the latest build task to enter

（3） Click after entering “ Check the log ”（ Only the log of pressure measurement period is displayed ）

8.2 View the business error log

（1） according to 8.1 Perform the following steps , After pressure test , Click on “ Check out the full log ”

（2） Slide down to see the error report （ Only the log of pressure measurement period is displayed ）

Four 、 exception handling

9. Clean up the pressure measurement data

（1） Get into Coding Project Click “ Create a build plan ”

（2） choice “ Clean up the cluster database ” Template

（3） Fill in the information according to the template , Click when finished “ determine ”

（4） After entering the new page, click return in the upper left corner

（5） Can be viewed in all or ungrouped , To clean up, click build , Clean up after construction

Be careful ： Please take a screenshot of the data before cleaning ！

10. Restart the pressure measurement cluster

（1） Get into Coding Project Click “ Create a build plan ”

（2） choice “ Restart the pressure measurement cluster ” Template

（3） Fill in the information according to the template , Click when finished “ determine ”

（4） After entering the new page, click return in the upper left corner

5、 ... and 、FAQ

1. Unable to connect to the pressure test service when the pressure test is executed

Problem analysis ：Coding Unable to successfully access the pressure test cluster

resolvent ： stay TKE Add Coding exit ip White list , Detailed steps reference ：TKE Add an Internet access white list to the cluster - cloud + Community - Tencent cloud

2. The number of threads generating pressure is unstable

resolvent ： You need to add a new one in the back-end listener of the script tag,TAG_Random ${__Random(0000000000,9999999999,)}, Details are as follows ：

3. The number of concurrency before the end of the pressure test 、QPS、 Bandwidth is climbing

resolvent ： For known problems , The pressure measurement results of this section can be ignored .

4. Grafana View normal , However, an error is reported after pressure measurement for a period of time 502

Problem analysis ： Now explain influxdb The database is full , It is usually caused by writing too many error messages

resolvent ： clear influxdb database

The detailed steps ： Please refer to section 9 Chapter clean up the pressure measurement data

5. Cannot upload more than 20M Script or data file

Problem analysis ：Coding Limit the size of the uploaded file

resolvent ： adopt git Upload

The detailed steps ： Copy the warehouse address in the code warehouse URL, adopt git clone URL, Pull the code locally , Put the data file in the corresponding folder , Then upload to the code warehouse .

git clone URL #  Pull the code 
git add . #  Add all the files to be pushed 
git commit -m ' Interpretative sentence ' #  Submit the modified file to the local warehouse 
git push origin master #  Push to warehouse 

Copy

6. Other case base documents

Pressure testing tool platform problem case base - cloud + Community - Tencent cloud