asp+|server|sqlserver| Solution | data | Problem existing problem:
1, all records on a table. No classification
2, when developing, because not to consider such a large amount of data. The query statement executes in the program, causing the slow speed
3, according to the relational database inserts the process principle, each inserts, constructs once the index query, then, will occupy the massive memory and the CPU resources, the speed will also greatly reduce. In the case of 100 records in the table inserted with the case of 10,000 records inserted, speed and efficiency is completely different!
4, insert and query are in the same table. The number of concurrent processing may be more than 1000 peak.
5, according to the relational database query principle, if someone wants to query the record table, it will be such a mathematical expression
A record <=1k
Total 100,000 records, 20,000 growth per day
If you do not know the conditions, arbitrary query, that will be the case:
(1K * 100,000)/1024 = 10M
1 persons are 10M. If it's 200 people, it's going to be like this:
200*10m = 2000M (approx. 2G)
Such large data is taken out of the database. and download to the local view, the original is very large.
6, the input points of a lot of network speed or "cat" internet, speed must not keep up.
7, there are other data stored in the server and so on.
7, the server bandwidth is only a dedicated line 8M, even if the CPU can calculate the server to come over, the data can not send out, it was jammed!
As a result of the above problems, the following are the cases:
1, the Web server hard drive physically burned piece.
2, web site bandwidth is completely occupied, basically difficult to access.
3, the website page speed is extremely slow, the data transmission efficiency is low.
4, some input units because the network can not respond to his operation, sent packets can not return, can not complete the record input.
Solution (IDEA):
1, server update. (On the hardware)
2, the network bandwidth increased. (On the hardware)
3, the query in the database, the use of stored procedures, but in the hundred gigabit speed, the application of stored procedures and procedures of the basic query is not significantly different. (on the software).
4, when inserting a record, use the buffer table, every 10 minutes, the buffer table to the main record table to rewind the data. This will relieve the pressure on the master record table. Let the master record table deal specifically with the query action (on the software)
5, the query, the use of text read out records, because based on the underlying system of the reference to move, query efficiency will be increased by 100 times times. However, Fileobjectsystem component support is required. Security to consider. (On software)
If no measures are taken, the problems that may arise:
The database is overwhelmed and the hard drive will burn again.
The server CPU has been running at 100% full load.
The program system crashed completely.
The data cannot be inserted instantly and cannot be immediately responsive.
Unable to count and track.
The sites are not functioning properly.