it happened after I upgrade the MySQL 5.7 directly to MySQL 8.0
In my mind, the best way to carry out any upgrade on MySQL is to delete your existing version of MySql and install a brand new version. (Obviously make sure you have a few backups in different locations in case something goes wrong)
Then once the new version is installed, restore the MySQL.sql dump file. When you do this each record in the .sql file is written to the database ensuring all the new requirements of the new version are in place. (This is the safest way and you are guaranteed that the content of the DB is correct because it was created by the new version- as opposed to some faulty upgrade process that goes wrong)
BUT before you do the restore, Export your BSV and then delete it in the configurator and re-create it by importing the BSV. Then publish the BSV. (It may be a good idea to re-install the AIM server from start with the new MySQL v8,00 version, just so there is a clean install with the MySQL V8.00 setup).
Once you have published then run the .sql restore process and everything should be good, unless MySQL V8 is not compatible with AIM
If I had some time on my hands I would do this and see if v8.00 makes a 2 x difference because that is a big claim that warrants an upgrade.
IMHO, I think your upgrade process may have been flawed and you would need to follow the above process for a proper V8 test outcome
