Due to various reasons such as version compatibility, the index of dedecms is actually a bit confusing. If the index is set appropriately, the speed of dedecms HTML generation will be affected mainly when obtaining a list of articles that are not sorted by default. Due to the need to reorder the data, When the volume is large, the speed will be very unsatisfactory. You can easily optimize it through the following steps:
1. Enter phpmyadmin and delete the indexes of the dedecms site dede_archives except the index of the ID primary key;
2 , use SQL to create the following index:
Alter TABLE `dede_archives` ADD INDEX `click` (`click`);
Alter TABLE `dede_archives` ADD INDEX `typeid` (`typeid`);
Alter TABLE `dede_archives` ADD INDEX `arcrank` (`arcrank`);
Alter TABLE `dede_archives` ADD INDEX `sortrank` (`sortrank`);
Alter TABLE `dede_archives` ADD INDEX `senddate` (`senddate` );
Alter TABLE `dede_archives` ADD INDEX `pubdate` (`pubdate`);
Alter TABLE `dede_archives` ADD INDEX `litpic` (`litpic`);
Alter TABLE `dede_archives` ADD INDEX `typeid2` (`typeid2`);
In the range of data volume of about 1W-10W, after such optimization, if the content page does not have relevant article tags, the generation speed will be three to five times faster
If there are relevant article tags, it will be two to three times faster