Hi !

After updating from 3.2.4 to 3.2.7, there is a ridiculously HUGE difference of Dashboard "Last issues" widget's loading times, that greatly affects system load on the DB server.
I have a split-setup configuration: one server is DB-only and another server is for zabbix-server and frontend.

I turned on debugging and tested 2 scenarios:
1. Only 1 user (Super Admin) online on the frontend - DB server load = near 0
2. Real-world scenario with 9-12 users online - DB server load = 12 - 14 (on the "user" side, NOT I/O !)
On both cases, zabbix-server WAS running.
There are 2 files attached that represent the SQL profile for each case, only on the "Last Issues" widget, of course.

Note that a lot of time is spent on SELECT DISTINCT queries.

Please help me investigate this critical issue.
I can make all kind of tests, even SQL profile v3.2.4 in the exact same environment.