gogoWebsite

1. Phenomenon

More than 30,000 ids were found

Then use

EntityWrapper ew = new EntityWrapper<>();
 (TableFieldConstant.F_AUTH_RESULT_ID, ids);

Query will be slow

2 reasons

Followed mybatis-plus source code

 protected String formatSqlIfNeed(boolean need, String sqlStr, Object... params) {
        if (need && !(sqlStr)) {
            if ((params)) {
                for(int i = 0; i < ; ++i) {
                    String genParamName = "MPGENVAL" + ();
                    sqlStr = (("{%s}", i), ("#{%.%s}", (), genParamName));
                    (genParamName, params[i]);
                }
            }

            return sqlStr;
        } else {
            return null;
        }
    }

The problem arises in

sqlStr = (("{%s}", i), ("#{%.%s}", (), genParamName));

Testing the replacement test. It is found that when the data volume is large, it will take time to replace it. The test has traversed 30,000 times and spliced ​​from 1 to 30,000. The replacement takes more than 20 seconds.

The test of apache-commons-lang took more than 7 seconds

3 Summary

Change the batch query using mybaits to handwritten SQL query and the problem is solved afterwards

Be cautious when using mybatis-plus batch operation. Try to write SQL as much as possible.

This problem has been solved after asking mybatis-plus friends. You can upgrade the jar version