Recently, I should write an efficient bulletin board program. This program is running to receive the amount of access to 2000, so the performance must be high, lower the server burden, but the network speed is not too slow.
From this, I considered two aspects:
1. The database must be SQL, most operational storage procedures.
2. When the data is added to the database, the information is stored in the database, and to generate a .html file, only one related .html link will reduce the burden of the server when client access.
It's almost exhausted, save the first. . Store again.