Can you explain the entire Load testing process in detail?

Can you explain the entire Load testing process in detail?Planning of the Test:Creating Vusers.Creating scenario.Running the created scenarios.Monitoring /observing the scenarios.Finally analyzing the test results.A: Planning of the Test: here we plan the test in such a way that it servers the objective of the load testing. I.e. creating the scenarios that will server the load testing process in order to reach out objective of testing.B: Creating Vusers: Creating vusers are nothing but creating the scripts by recording different functionality of the application. These scripts will have the tasks / transaction that will be run by vusers (virtual users).C: Creating the scenario: Creating the scenario is the important step in load testing process. Creating scenario includes number vusers, vusers scripts, The transactions that made the scenario, and load generation machines etc…. We will create a scenario in controller. There are normally 2 types of scenarios. 1. Manual scenario 2. Goal oriented scenario.D: Running the scenarios: Running the scenario means allowing vusers to run the scripts so that the load will be applied simultaneously on the server. After creating the scenario in controller, we will schedule the scenario and then run the scenario.E: Monitoring the scenarios: Monitoring the scenario means we will observe the different resources while the scenario is running. These resources include but not limited to System resources, Web resources, Network resources, Server resources, Application server resources, Data streaming resources, Database server resources, security resources etc…. After monitoring these resources if we notice any abnormal metrics then contact the related server administrators or the personnel who is responsible for that and they will investigate on this issue.F: Analyze the test results: After running the scenario, we will go to Loadrunner analyzer and create the respective graphs for different servers, and analyze the metrics with the benchmark results/metrics to see if the results are near to those benchmarks or they are degraded. If they are degraded, then analyze why this degradation happened? This you can do by analyzing the server logs and find out if database server is taking long time, then send those logs to database administrator to work on this. If application server is taking long time to process requests then contact application server administrator to work on this issue. The same way if requests are in queue for a long time at web server, i.e load distribution is not handled properly by load generator then contact the appropriate personnel to solve this issue.