The "large" case is missing a factor of dx in the definition of both A and AT. I am not changing it for now, so that the demo results will more closely match those of the paper. In any event, using a value of dx that is larger than that dictated by your problem can make things better conditioned, so it"s best to simply rescale the results.
SHOW FULL COLUMNS FROM `jrk_downrecords` [ RunTime:0.002912s ]
SELECT `a`.`aid`,`a`.`title`,`a`.`create_time`,`m`.`username` FROM `jrk_downrecords` `a` INNER JOIN `jrk_member` `m` ON `a`.`uid`=`m`.`id` WHERE `a`.`status` = 1 GROUP BY `a`.`aid` ORDER BY `a`.`create_time` DESC LIMIT 10 [ RunTime:0.090204s ]
SHOW FULL COLUMNS FROM `jrk_tagrecords` [ RunTime:0.001378s ]
SELECT * FROM `jrk_tagrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 20 [ RunTime:0.001258s ]
SHOW FULL COLUMNS FROM `jrk_member` [ RunTime:0.001260s ]
SELECT `id`,`username`,`userhead`,`usertime` FROM `jrk_member` WHERE `status` = 1 ORDER BY `usertime` DESC LIMIT 10 [ RunTime:0.005358s ]
SHOW FULL COLUMNS FROM `jrk_searchrecords` [ RunTime:0.001381s ]
SELECT * FROM `jrk_searchrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 5 [ RunTime:0.006970s ]
SELECT aid,title,count(aid) as c FROM `jrk_downrecords` GROUP BY `aid` ORDER BY `c` DESC LIMIT 10 [ RunTime:0.022034s ]
SHOW FULL COLUMNS FROM `jrk_articles` [ RunTime:0.000970s ]
UPDATE `jrk_articles` SET `hits` = 2 WHERE `id` = 26534 [ RunTime:0.251690s ]
