ASP Performance Test Part II (EXT) (i)

First, the purpose of testing
Compiled as follows:
The first part of this paper examines some basic problems in ASP development, and gives some performance test results to help readers understand the effect of the code put into the page on the performance. ADO is a common, Easy-to-use database interface developed by Microsoft, and it turns out that interaction with the database through ADO is one of the most important applications of ASP, in the second part, we study this problem.
ADO provides a wide range of functionality, so the biggest difficulty in preparing this article is how to define the scope of the problem. Considering that extracting a large amount of data can significantly increase the load on the Web server, we decide that the main purpose of this section is to find out what is the optimal configuration for operating an ADO recordset. However, even narrowing the scope of the problem, we still face great difficulties, because ADO can have many different ways to accomplish the same task. For example, a recordset can be extracted not only from the Recordset class, but also through the connection and command classes, and even after the Recordset object is available, there are many operational methods that can dramatically affect performance. However, as in the first part, we will cover the widest possible range of issues.
Specifically, the objective of this section is to gather enough information to answer the following questions:
Should adovbs.inc be referenced by including references?
Should you create separate connection objects when using recordsets?
What is the best way to extract the recordset?
which cursor type and record locking mode are most efficient?
Should a local recordset be used?
What is the best way to set recordset properties?
Which method of referencing a recordset field value is most efficient?
Is it a good way to collect output with a temporary string?