Standard plugins may not cause perf issue. But if you designed your own, it can be soyrce of bad perf.

First a good test would be to try with brand new database : is perf bad without data ?
If yes : your infrastructure is the issue.
If no : install all your plugins : is perf bad with plugins ?
If yes : your plugins is the issue.
If no : install backup of data : if perf is bad, your data is the issue.

thanks for your reply.

I did new install. perf good
i install plugin : perf good
I import data : perf bad !!!

i have issue on data ... But how can I fixed it ?

is it possible to send you my backup database to check the issues ?

I have restart the PC from Projeqtor install today.

when I'm logging to Projeqtor and check the log files, I found some errors:

2017-10-11 08:28:21.533 ** ERROR ** [V6.4.2] Exception-[70100] SQLSTATE[70100]: : 1317 Query execution was interrupted
2017-10-11 08:28:21.534 ** ERROR ** [V6.4.2] For query : select * from indicatorvalue where idle='0' and ( ( warningTargetDateTime<='2017-10-11 08:28:21' and (warningSent='0' or code = 'YEARLY')) or ( alertTargetDateTimequery called at [/var/www/projeqtor/model/persistence/SqlElement.php:2253]
2017-10-11 08:28:21.534 ** ERROR ** [V6.4.2] #1 SqlElement->getSqlElementsFromCriteria called at [/var/www/projeqtor/model/Cron.php:372]
2017-10-11 08:28:21.534 ** ERROR ** [V6.4.2] #2 Cron->checkDates called at [/var/www/projeqtor/model/Cron.php:312]
2017-10-11 08:28:21.534 ** ERROR ** [V6.4.2] #3 Cron->run called at [/var/www/projeqtor/model/Cron.php:270]
2017-10-11 08:28:21.534 ** ERROR ** [V6.4.2] #4 Cron->relaunch called at [/var/www/projeqtor/tool/cronRelaunch.php:30]

Logged query does not seem to have issue.
Possibly it is due to stop of MySql.